Обсуждение: I can see beta now
A month ago I warned that we had an unusually high number of open items: http://archives.postgresql.org/pgsql-hackers/2009-01/msg00321.php Fortunately, thanks to a lot of hard work, my list of open items has shrunk from +200 to 44: http://momjian.us/cgi-bin/pgsql/open Now, that list is _imperfect_ and reflects items that are also on the commit fest page. I have emailed individually asking about most of the items but if you have feedback on any of them, please let me know. I also have personal email collections for Magnus, Marc, and Joe Conway. There are now seven unapplied patches on the commit-fest page: http://wiki.postgresql.org/wiki/CommitFest_2008-11 not counting the SE-PostgreSQL and "Recovery, Replication, Hot Standby" patches. I can now see us closing the existing items in the next several weeks and preparing for 8.4 beta. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Mon, Feb 9, 2009 at 9:39 AM, Bruce Momjian <bruce@momjian.us> wrote: > There are now seven unapplied patches on the commit-fest page: > > http://wiki.postgresql.org/wiki/CommitFest_2008-11 > > not counting the SE-PostgreSQL and "Recovery, Replication, Hot Standby" > patches. > > I can now see us closing the existing items in the next several weeks > and preparing for 8.4 beta. Is there any agreement about which committers will be handling which of the remaining CommitFest patches? Is any help needed from the rest of the community? I think Alvaro is about ready to commit the last piece of "autovacuum and reloptions", and as for "Reducing some DDL Locks to ShareLock" there is currently nothing for a committer to do as there is no updated patch. Heikki is working on infrastructure changes for recovery and Hot Standby. That still leaves the following patches in need of some action (commit, reject, bump to 8.5, or request changes) by a committer: - SE-PostgreSQL Lite - GIN fast insert - B-Tree Emulation for GIN - Improve Performance of Multi-Batch Hash Join for Skewed Data Sets - Proposal of PITR performance improvement - updated hash functions ...Robert
Robert Haas wrote: > On Mon, Feb 9, 2009 at 9:39 AM, Bruce Momjian <bruce@momjian.us> wrote: > > There are now seven unapplied patches on the commit-fest page: > > > > http://wiki.postgresql.org/wiki/CommitFest_2008-11 > > > > not counting the SE-PostgreSQL and "Recovery, Replication, Hot Standby" > > patches. > > > > I can now see us closing the existing items in the next several weeks > > and preparing for 8.4 beta. > > Is there any agreement about which committers will be handling which > of the remaining CommitFest patches? Is any help needed from the rest > of the community? No. I talked to Oleg on IM and he is waiting for an official review. Is someone going to review his work or should he commit it (with Teodor) because they know this area of the code better than anyone else? > I think Alvaro is about ready to commit the last piece of "autovacuum > and reloptions", and as for "Reducing some DDL Locks to ShareLock" Good. > there is currently nothing for a committer to do as there is no > updated patch. Heikki is working on infrastructure changes for > recovery and Hot Standby. That still leaves the following patches in Heikki is responsible for this group of patches. > need of some action (commit, reject, bump to 8.5, or request changes) > by a committer: > > - SE-PostgreSQL Lite > - GIN fast insert > - B-Tree Emulation for GIN > - Improve Performance of Multi-Batch Hash Join for Skewed Data Sets > - Proposal of PITR performance improvement > - updated hash functions Yep. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Bruce Momjian <bruce@momjian.us> writes:
> I talked to Oleg on IM and he is waiting for an official review. Is
> someone going to review his work or should he commit it (with Teodor)
> because they know this area of the code better than anyone else?
Obviously they know the innards of GIN better than the rest of us,
but I still had some concerns about the API to the rest of the system.
regards, tom lane