Skip site navigation (1) Skip section navigation (2)

Re: Uh, I change my mind about commit_delay + commit_siblings (sort of)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Uh, I change my mind about commit_delay + commit_siblings (sort of)
Date: 2012-07-02 14:32:18
Message-ID: CA+Tgmobjkt-T5DVru008tSouMJ0XAOeURn721gVh+nxoauJ04g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jun 28, 2012 at 6:01 PM, Daniel Farina <daniel(at)heroku(dot)com> wrote:
> On Thu, Jun 28, 2012 at 2:32 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
>> On 28 June 2012 22:22, Daniel Farina <daniel(at)heroku(dot)com> wrote:
>>> All in all, I don't think this can be a very productive discussion
>>> unless someone just pitches a equal or better name overall in terms of
>>> conciseness and descriptiveness.  I'd rather optimize for those
>>> attributes.  Old advice is old; that's the nature of the beast.
>>
>> Robert suggested wal_flush_delay, which does more accurately describe
>> what happens now.
>
> Well, I learned something from reading this name, having not followed
> the mechanism too closely.  I like it.

I've committed this now.  In the absence of a clear consensus to
rename the GUC, I contented myself with a further overhaul of the
documentation, which will hopefully make things clear at least for
people who read the documentation.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-07-02 14:33:58
Subject: Re: [PATCH] Lazy hashaggregate when no aggregation is needed
Previous:From: Peter GeogheganDate: 2012-07-02 14:19:56
Subject: Re: enhanced error fields

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