Re: Draft release notes complete

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: pgsql-hackers@postgresql.org

Date: 2012-05-21T18:10:09Z

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 →

Expose track_iotiming information via pg_stat_statements.
- 5b4f34661143 9.2.0 cited
Rewrite GiST support code for rangetypes.
- 80da9e68fdd7 9.2.0 cited
Clean up a couple of box gist helper functions.
- d50e1251946a 9.2.0 cited
Replace the "New Linear" GiST split algorithm for boxes and points with a
- 7f3bd86843e5 9.2.0 cited

> For these reasons, it may be timely and appropriate, from a purely
> advocacy point-of-view, to call our new group commit "group commit" in
> release notes and documentation, and announce it as a new feature.

First, shouldn't we be having this discussion on -advocacy?

To date, I've been calling it "better group commit".

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com