Postgres Pro
Downloads
Home   >   mailing lists

Re: problems with set_config, work_mem, maintenance_work_mem, and sorting - Mailing list pgsql-performance

From Claudio Freire
Subject Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Date
Msg-id CAGTBQpbok6o8Z0vBVf4kDaAqOdSowbRnY=K5DR2yxD7n+PX6zA@mail.gmail.com
Whole thread Raw
In response to Re: problems with set_config, work_mem, maintenance_work_mem, and sorting  (Jon Nelson <jnelson+pgsql@jamponi.net>)
Responses Re: problems with set_config, work_mem, maintenance_work_mem, and sorting  (Ants Aasma <ants.aasma@eesti.ee>)
List pgsql-performance
Tree view 
On Tue, Feb 28, 2012 at 8:00 PM, Jon Nelson <jnelson+pgsql@jamponi.net> wrote:
> I cranked the logging /all/ the way up and isolated the server.
> I suspect that your theory is correct.

Another option, depending on your SQLA version, when connections are
sent back to the pool, I seem to remember they were reset. That would
also reset the work_mem, you'd still see the same pid on PG logs, but
it's not the same session.

pgsql-performance by date:

Previous
From: Jon Nelson
Date:
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Next
From: Stefan Keller
Date:
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?