Re: GUC assign hooks (was Re: wal_buffers = -1 and SIGHUP)

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <robertmhaas(at)gmail(dot)com>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <mailings(at)oopsware(dot)de>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GUC assign hooks (was Re: wal_buffers = -1 and SIGHUP)
Date: 2011-04-04 12:07:00
Message-ID: 4D996E14020000250003C1C7@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> On Sun, Apr 3, 2011 at 1:26 PM, Tom Lane wrote:

>> It would probably take less than a day to flesh out this idea and
>> make it happen, but it does seem like a rather large change for
>> late alpha.

> what we're trying to avoid is committing new stuff that may require
> additional cleanup, not cleaning up the stuff we already did
> commit. Once we get to beta I'll be less enthusiastic about making
> changes like this

+1 for fixing it, with full agreement with Robert's project
management perspective on the issue.

Having worked in this area a bit I definitely see the need in
general, and for auto-tuning we pretty much have to do this to get it
right. I think we should be edging into more auto-tuning
capabilities as we figure them out, making this all the more
important.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2011-04-04 14:25:54 Re: Process local hint bit cache
Previous Message Alexander Korotkov 2011-04-04 11:35:13 Re: Proposal: q-gram GIN and GiST indexes