Re: Draft release notes complete

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndQuadrant.com>

To: Peter Geoghegan <peter@2ndquadrant.com>

Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-05-10T12:25:54Z

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

On 10 May 2012 13:11, Peter Geoghegan <peter@2ndquadrant.com> wrote:

> Why can't we call group commit group commit (and for that matter,
> index-only scans index-only scans), so that people will understand
> that we are now competitive with other RDBMSs in this area? "Improve
> performance of WAL writes when multiple transactions commit at the
> same time" seems like a pretty bad description, since it doesn't make
> any reference to batching of commits.  Also, I don't think that the
> placement of this as the second to last performance feature is
> commensurate with its actual importance.

Agreed.

Group Commit is a recognised term and also one where other DBMS, e.g.
Marea have included that feature recently.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services