Robert Haas <[email protected]> writes:
> On Thu, Nov 11, 2010 at 1:23 PM, Tom Lane <[email protected]> wrote:
>> I do think that something based around a settable-per-table caching
>> percentage might be a reasonable way to proceed. But the devil is in
>> the details, and we don't have those yet.
> I think one of the larger devils in the details is deciding how to
> estimate the assumed caching percentage when the user hasn't specified
> one.
I was imagining something very similar to the handling of seq_page_cost,
ie, there's a GUC controlling the system-wide default and then you can
override that per-table. But the real question is whether per-table
is a useful granularity to control it at. See my later message.
regards, tom lane
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
