Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Date: 2012-02-28 20:51:54
Message-ID: 10857.1330462314@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> writes:
> On Tue, Feb 28, 2012 at 1:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Jon Nelson <jnelson+pgsql(at)jamponi(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Jon NelsonDate: 2012-02-28 21:38:12
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Previous:From: Stefan KellerDate: 2012-02-28 20:48:45
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group