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

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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(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>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Uh, I change my mind about commit_delay + commit_siblings (sort of)
Date: 2012-07-03 03:28:33
Message-ID: 20120703032833.GD25966@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jun 28, 2012 at 08:17:53PM +0100, Peter Geoghegan wrote:
> On 28 June 2012 20:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > See VACUUM FULL for a recent counterexample --- we basically jacked it
> > up and drove a new implementation underneath, but we didn't change the
> > name, despite the fact that we were obsoleting a whole lot more folk
> > knowledge than exists around commit_delay.
> >
> > Of course, there were application-compatibility reasons not to rename
> > that command, which wouldn't apply so much to commit_delay.  But still,
> > we have precedent for expecting that we can fix external documentation
> > rather than trying to code around whatever it says.
> 
> I'm sure you're right to some degree. We can rely on some, maybe even
> most users to go and learn about these things, or hear about them
> somehow. But why should we do it that way, when what I've proposed is
> so much simpler, and has no plausible downside?

FYI, the release notes are the big place we should talk about this new,
better behavior.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2012-07-03 06:13:21
Subject: Re: enhanced error fields
Previous:From: Tom LaneDate: 2012-07-03 03:25:12
Subject: Re: Event Triggers reduced, v1

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