Re: controlling memory management with regard to a specific query (or groups of connections)

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Jonathan Vanasco <postgres(at)2xlp(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: controlling memory management with regard to a specific query (or groups of connections)
Date: 2015-11-20 17:28:28
Message-ID: CAMkU=1wsoXjedqnozk98LAvt+1VNtOHEejyFC6tdAjzX1WhEtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 18, 2015 at 5:10 PM, Jonathan Vanasco <postgres(at)2xlp(dot)com> wrote:
> As a temporary fix I need to write some uploaded image files to PostgreSQL until a task server can read/process/delete them.
>
> The problem I've run into (via server load tests that model our production environment), is that these read/writes end up pushing the indexes used by other queries out of memory -- causing them to be re-read from disk. These files can be anywhere from 200k to 5MB.

Are you storing them as large object, or as bytea? Can you share the
load testing scripts?

Cheers,

Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message anj patnaik 2015-11-20 23:09:45 error messages not getting logged when running script from cron
Previous Message Adrian Klaver 2015-11-20 15:32:58 Re: What could cause CREATE TEMP... "could not read block" error?