Horton

Re: Draft release notes complete

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>, Jeff Janes <jeff.janes@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-15T16:51:33Z
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 →

  1. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

On Mon, May 14, 2012 at 3:21 PM, Peter Geoghegan <peter@2ndquadrant.com> wrote:
> The mere ability to notice that an XLogFlush() call is unnecessary and
> fastpath out could be argued to be an aboriginal group commit,
> predating even commit_delay, as could skipping duplicate fsync()
> requests in XLogWrite(), which I think Jeff pointed out, but I don't
> think anyone actually takes this position.

Well, Tom appears to have to have he'd implemented group commit in 2002.

http://archives.postgresql.org/pgsql-hackers/2002-10/msg00331.php

More accurately, he seems to have thought that group commit was
already there, and he'd improved it.  So saying that we're getting it
for the first time ten years later seems pretty odd to me.

I don't deny that the new feature is a significant improvement under
the right circumstances.  But I still maintain it's an improvement of
something that was already there, rather than something new.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company