Re: wrapping up this CommitFest (was Re: knngist - 0.8)
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2011-03-04T22:29:15Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Further refine patch for commenting operator implementation functions.
- 908ab8028640 9.1.0 cited
-
Fix citext's upgrade-from-unpackaged script to set its collation correctly.
- 94be9e3f0ca9 9.1.0 cited
-
Mark operator implementation functions as such in their comments.
- 94133a935414 9.1.0 cited
-
Add KNNGIST support to contrib/btree_gist.
- 8436489c81c2 9.1.0 cited
-
Fix plpython breakage detected on certain Fedora machines on buildfarm.
- 4c966d920fb7 9.1.0 cited
On Tue, 2011-03-01 at 22:56 +0000, Simon Riggs wrote: > On Tue, 2011-03-01 at 12:42 -0800, Josh Berkus wrote: > > > That response is just dodging the hard question, so whatever. Tom's > > > cleanup is not going to break things, or at least it's going to fix > > > more than it breaks on net. Sync rep, on the other hand, is going to > > > do the opposite, probably by a large margin. > > > > Well, we need to at least give Simon and Fujii a chance to respond > > during their respective daytime hours. > > Friday is a reasonable deadline. I'm not going to be committing Sync Rep today. It's technically in very good shape, but some of the conceptual issues aren't clear enough on a Friday night to make it sensible for me to commit to PostgreSQL, given we must support it for 5 years if I do. I believe those things are resolvable for 9.1, probably fairly soon, but I'm not going to rush a commit just to hit a deadline. That isn't the Way of Quality that we have followed for so long. I'll let y'all discuss what to do next. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services