Re: commit fests (was Re: primary key error message) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: commit fests (was Re: primary key error message)
Date
Msg-id 16245.1264116406@sss.pgh.pa.us
Whole thread Raw
In response to Re: commit fests (was Re: primary key error message)  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: commit fests (was Re: primary key error message)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: commit fests (was Re: primary key error message)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Peter Eisentraut wrote:
>> But I don't think that should mean everyone has to drop everything when
>> the clock strikes midnight and must now only look at things that the
>> magic commitfest page has pre-approved.  

> Well, we used to have the idea of a feature freeze ... is that going to 
> apply at the end of the commitfest?

Even a feature freeze would not IMO prevent considering the sort of
small adjustment Peter was suggesting.  We will doubtless be making
far larger adjustments than that even quite late in the release cycle.
(Particularly in the new HS/SR code.)

I thought his patch wasn't a particularly good idea, but I didn't have
a problem with it from a schedule or process standpoint.

If you want an example of something I *do* have a process problem
with, it's Kevin Grittner's attempts to get people to put a
significant number of cycles into thinking about true serializability.
Right now is not the time for that to be happening.  I've been
politely ignoring that thread, but ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: 8.5 vs. 9.0
Next
From: "Kevin Grittner"
Date:
Subject: Re: commit fests (was Re: primary key error message)