On Thu, Jan 7, 2010 at 10:20 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> OK, we have a proposal on the table to bump some patches from this >> CommitFest to free up more committer resources, particularly Tom, to >> work on Hot Standby and Streaming Replication and attempt to >> accelerate the process of getting 8.5 out the door. This proposal >> needs input from the community. The affected patches are: > >> - Listen/Notify Rewrite. >> - Writeable CTEs. >> - more frame options for window functions >> - knngist >> - rbtree > > Looking at this list again, it strikes me that the listen/notify rewrite > might need to go in so that we have a sane framework for listen/notify > with HS. Treating pg_listener as a replicatable table isn't sane at > all, whereas with a message-driven notify mechanism we have at least got > the possibility of shipping the messages to the standby (via WAL) and > having listeners there. I don't want to say we'd actually implement > that in 8.5, but shipping pg_listener tuple updates is just completely > nuts. > > The other four things have no apparent connection to HS/SR so I think > they could be punted without creating technical issues. Whether this > is really necessary from a schedule viewpoint is not clear yet. > > My thought about it would be to put these four on the back burner; > not necessarily bounce them right away, but not put any effort into > them until we have dealt with the other stuff in the January CF. > At that point we should have a feel for where we are schedule-wise, > and in particular we'll know whether SR is in or not ;-)
I think it might be time to revisit this issue. SR is in, and we have a week left in the CF, and we have all of the above patches plus 5 small ones left to deal with. rbtree is close to being committable, I think; knngist has not been reviewed yet; you (Tom) have claimed the frame options patch but I haven't seen any update on it in a while; I doubt either of the other two are ready to commit but I'm not sure how far they have to go. 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
