On Wed, Jan 6, 2010 at 3:03 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Fujii Masao wrote: >>> I've done that in my git branch. >> >> Could you push that git branch to a public place? > > Ahh, sorry, forgot that again. It's there now, at > git://git.postgresql.org/git/users/heikki/postgres.git, branch > 'replication'.
I'm feeling like we're running out of time to get this committed. Committing large patches late in the release cycle is a recipe for a buggy beta, possibly a long beta, and a buggy release, and we're now down to 8 days before the start of the final CommitFest, after which our schedule indicates that we expect to put out an alpha and a beta relatively quickly. If this isn't ready to go, maybe we need to postpone it to 8.6. We've already had a bunch of bug reports (some of which have been fixed) as a result of HS, and I don't see any reason to believe that this isn't going to have the same problem. Personally, I would rather have a release without SR in June or July than a release with SR in August or September. We already have too many good features in the tree to hold up the whole process for patches that aren't ready yet - though like everyone else, I think this is a killer feature. Thoughts? ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers