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

From Jon Nelson
Subject Re: problems with set_config, work_mem, maintenance_work_mem, and sorting
Date
Msg-id CAKuK5J2rHEM_GCoCTPyw3ajn3yvg3QFX6apSiYbvJULDt_TGyg@mail.gmail.com
Whole thread Raw
In response to Re: problems with set_config, work_mem, maintenance_work_mem, and sorting  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: problems with set_config, work_mem, maintenance_work_mem, and sorting  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Tue, Feb 28, 2012 at 1:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jon Nelson <jnelson+pgsql@jamponi.net> writes:
>> The config shows 128MB for work_mem and 2GB for maintenance_work_mem.
>> 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.
The logline format is:

log_line_prefix = '%t %d %u [%p]'

and I believe %p represents the pid, and also that a pid corresponds
to a backend. Therefore, same pid == same backend == same connection
== same session. Many transactions within a session.


--
Jon

pgsql-performance by date:

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