Re: GUC variable for setting number of local buffers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Bertheau <twanger(at)bluetwanger(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: GUC variable for setting number of local buffers
Date: 2005-03-20 17:36:55
Message-ID: 7978.1111340215@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Markus Bertheau <twanger(at)bluetwanger(dot)de> writes:
>> It's already true that the individual buffers, as opposed to the buffer
>> descriptors, are allocated only as needed; which makes the overhead
>> of a large local_buffers setting pretty small if you don't actually do
>> much with temp tables in a given session. So I was thinking about
>> making the default value fairly robust, maybe 1000 (as compared to
>> the historical value of 64...).

> Why does the dba need to set that variable at all then?

Because you do have to have a limit. You want the thing trying to keep
all of a large temp table in core?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2005-03-20 17:43:07 what to do with backend flowchart
Previous Message Tom Lane 2005-03-20 17:35:47 Re: read-only planner input