Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to
Date: 2010-01-29 20:25:46
Message-ID: 1264796746.13782.55.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, 2010-01-29 at 14:04 -0500, Tom Lane wrote:
> sriggs(at)postgresql(dot)org (Simon Riggs) writes:
> > Log Message:
> > -----------
> > Augment WAL records for btree delete with GetOldestXmin() to reduce
> > false positives during Hot Standby conflict processing. Simple
> > patch to enhance conflict processing, following previous discussions.
> > Controlled by parameter minimize_standby_conflicts = on | off, with
> > default off allows measurement of performance impact to see whether
> > it should be set on all the time.
>
> WTF? Simon, this seems to be getting way way beyond anything the
> community has agreed to. Particularly, inventing GUCs is not something
> to be doing without consensus.

If you or anybody else would like me to revoke it then I am happy to do
that, with no problem or argument. I agree it hasn't had discussion,
though am happy to have such a discussion.

The commit is a one line change, with parameter to control it, discussed
by Heikki and myself in December 2008. I stand by the accuracy of the
change; the parameter is really to ensure we can test during beta.

I imagined such a minor addition would pass without comment. This is not
the same patch not-being-discussed on the other thread, which is too
complex for a commit without review. It is a separate change altogether,
although it does relate to conflict processing. In any case I would
never commit a patch while discussion on it continues.

--
Simon Riggs www.2ndQuadrant.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2010-01-30 01:46:57 pgsql: Add plperl.on_perl_init setting to provide for initializing the
Previous Message User Fxjr 2010-01-29 19:46:38 npgsql - Npgsql2: Added Tools/NAnt to Npgsql2

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-29 20:28:35 Re: PG 9.0 and standard_conforming_strings
Previous Message Andrew Dunstan 2010-01-29 20:00:09 odd output in initdb