Re: reducing the overhead of frequent table locks - now, with WIP patch - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: reducing the overhead of frequent table locks - now, with WIP patch
Date
Msg-id BANLkTind5HDwB36n_wv4835o7XzJ8kpvMw@mail.gmail.com
Whole thread Raw
In response to Re: reducing the overhead of frequent table locks - now, with WIP patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: reducing the overhead of frequent table locks - now, with WIP patch
Re: reducing the overhead of frequent table locks - now, with WIP patch
List pgsql-hackers
On Wed, Jun 8, 2011 at 5:44 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Jun 8, 2011 at 12:25 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> As a result of this, I've been insulted, told I have no respect for
>> process and even suggested there was a threat of patch war.
>
> Well, you've pretty much said flat out you don't like the process, and
> you don't agree with having a firm feature freeze.  I think it's a
> perfectly legitimate question to ask whether we're going to have to
> continually relitigate that point.  This is at least the second major
> dust-up on this point since the end of 9.1CF4, and there were some
> smaller ones, too.

Why do you address this to me? Many others have been committing
patches against raised issues well after feature freeze.

You do not wish to stop all patches, only those you disagree with. How
would I know you disagree with a patch without discussing it?

I note that you've claimed *everything* I have discussed is a new
feature, whereas everything you or others have done is an "open item".
You can claim that everything I suggest is a dust-up if you wish, but
who makes it a dust up and why?

The point I have made is that I disagree with a feature freeze date
fixed ahead of time without regard to the content of the forthcoming
release. I've not said I disagree with feature freezes altogether,
which would be utterly ridiculous. Fixed dates are IMHO much less
important than a sensible and useful feature set for our users. MySQL
repeatedly delivered releases with half-finished features and earned
much disrespect. We have never done that previously and I am against
doing so in the future.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Autoanalyze and OldestXmin
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Allow star syntax in GROUP BY, as a shorthand for all table columns