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 21:54:43
Message-ID: 27623.1330466083@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 2:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hmph ... does seem a bit weird. Can you turn on log_statements and
>> identify which operations aren't using the session values?

> I had log_min_duration_statement = 1000.

That's not really going to prove much, as you won't be able to see any
commands that might be setting or resetting the work_mem parameters.

> ... which is the ORM library (SQLAlchemy) doing a reflection of the
> table(s) involved.

Oh, there's an ORM involved?  I'll bet a nickel it's doing something
surprising, like not issuing your SET until much later than you thought.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Claudio FreireDate: 2012-02-28 22:41:34
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Previous:From: Kääriäinen AnssiDate: 2012-02-28 21:48:52
Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting

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