Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
On Tue, Feb 28, 2012 at 8:00 PM, Jon Nelson <jnelson+pgsql@xxxxxxxxxxx> 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.
--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
- References:
- problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
- Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
[Postgresql General]
[Postgresql PHP]
[PHP Users]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Home]
[Yosemite]