From: Simon Riggs <simon@2ndQuadrant.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: Guillaume Smet <guillaume.smet@gmail.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: New trigger option of pg_standby
Date: Wed, 27 May 2009 19:08:52 +0100
Message-ID: <1243447732.24860.316.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <4A1D74E9.2070505@dunslane.net>
References: <200905271608.n4RG8tW06393@momjian.us>
<1243443276.24860.279.camel@ebony.2ndQuadrant>
<4A1D74E9.2070505@dunslane.net>
On Wed, 2009-05-27 at 13:14 -0400, Andrew Dunstan wrote:
>
> Simon Riggs wrote:
> > My experience is that consensus/votes will be overruled by final
> > committer, if they disagree,
>
> That's a fairly strong statement.
I was attempting to be open and honest to allow us to face our faults,
as proposed, because I care about the health and efficiency of the
project. I expected your response and know you think my comments to be
blunt at times. We should worry about the people that don't speak their
mind, not those that do.
> I can't think of an occasion when this
> has happened on any matter of significance, and I can remember many
> times when Tom, Bruce and others have bowed to the consensus despite
> their own preferences.
It depends on what you regard as matters of significance and which parts
of the code you pay attention to. Committers can act as they choose; I
am merely pointing out that it isn't possible for non-committers to
follow through on any responsibility they may attempt to assert.
Specifically, trying to propose solutions, achieve consensus and develop
patches only works if the committer will agree with conclusions at the
end and you won't know until you get there. You can do a ton of work and
it can all be for nothing if the consensus opposes the committer. After
a while you reach the conclusion: Why do the work, why not just wait for
the opinion and then act? Less work and same speed.
> Bruce said the other day that we are trustees of the code, and I don't
> think I could put it better. I know I am conscious of that.
I doubt anyone reading this list feels any differently.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: simon@2ndQuadrant.com, andrew@dunslane.net, bruce@momjian.us, tgl@sss.pgh.pa.us, heikki.linnakangas@enterprisedb.com, masao.fujii@gmail.com, guillaume.smet@gmail.com, peter_e@gmx.net, Kevin.Grittner@wicourts.gov
Subject: Re: New trigger option of pg_standby
In-Reply-To: <1243447732.24860.316.camel@ebony.2ndQuadrant>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox