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

From Tom Lane
Subject Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Date
Msg-id 10857.1330462314@sss.pgh.pa.us
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  (Jon Nelson <jnelson+pgsql@jamponi.net>)
List pgsql-performance
Jon Nelson <jnelson+pgsql@jamponi.net> writes:
> On Tue, Feb 28, 2012 at 1:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Jon Nelson <jnelson+pgsql@jamponi.net> writes:
>>> Why does PostgreSQL /sometimes/ use the globally-configured values and
>>> sometimes use the values that come from the connection?

>> You sure those log entries are all from the same process?

> If I am understanding this correctly, yes. They all share the same pid.

Hmph ... does seem a bit weird.  Can you turn on log_statements and
identify which operations aren't using the session values?

            regards, tom lane

pgsql-performance by date:

Previous
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?
Next
From: Jon Nelson
Date:
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting