On Tue, Mar 1, 2011 at 1:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Mon, Feb 28, 2011 at 2:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Given that it is a contrib module, I personally wouldn't object to it
>>> getting patched later, like during alpha or beta. But somebody's got
>>> to do the work, and I've got a dozen higher-priority problems right now.
>
>> Well, we can argue about whether it's too late for 9.1 if and when a
>> patch shows up. Right now we don't have that problem.
>
> We do now ...
> http://archives.postgresql.org/pgsql-hackers/2011-03/msg00038.php
>
> Since we appear to be still holding the commitfest open for Sync Rep,
> I guess this ought to get reviewed.
Or else we should close the CommitFest and cut alpha4. Anyone have an
opinion on which way to go?
I think it's fair to say that Simon is working pretty actively on Sync
Rep and that the bug count is probably dropping rapidly. It seems a
shame to push sync rep out to 9.2 in that context. On the other hand,
the patch wasn't done at the beginning of the CommitFest, it wasn't
done at the scheduled end of the CommitFest, and it's still not done
now two weeks after the scheduled end of the CommitFest. If it gets
committed O(now), it's probably going to still have bugs and design
problems that will take at least a few more weeks to shake out, which
will directly add to the length of time that it takes to actually get
the release out the door.
I could go either way on this one.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company