Re: problems with set_config, work_mem, maintenance_work_mem, and sorting

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Date: 2012-02-28 23:43:37
Message-ID: CAGTBQpbok6o8Z0vBVf4kDaAqOdSowbRnY=K5DR2yxD7n+PX6zA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Feb 28, 2012 at 8:00 PM, Jon Nelson <jnelson+pgsql(at)jamponi(dot)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.

In response to

Responses

Browse pgsql-performance by date

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