Re: Draft release notes complete

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Robert Haas <robertmhaas@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-05-10T17:02:34Z

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

Attachments

release.diff (text/x-diff) patch

 On Thu, May 10, 2012 at 01:56:33AM -0400, Robert Haas wrote:
> On Wed, May 9, 2012 at 11:11 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > I have completed my draft of the 9.2 release notes, and committed it to
> > git.
> 
> Extra parens:
> Remove the spclocation field from pg_tablespace (Magnus Hagander, Tom Lane))
> Reduce overhead of creating virtual transaction id locks ((Robert
> Haas, Jeff Davis)

Done.

> The antecedent of "these" is unclear:
> Allow backends to detect postmaster death via a pipe read failure,
> rather than polling (Peter Geoghegan, Heikki Linnakangas)
> These are internally called "latches".

Fixed.

> Missing comma:
> Cancel queries if clients get disconnected (Florian Pflug Greg Jaskiewicz)

Fixed by some else.

> You mean "effect":
> Such casts have no affect.

Fixed.

> 
> I think all three of these are the same thing:
> Avoid table and index rebuilds when NUMERIC, VARBIT, and temporal
> columns are changed in compatible ways (Noah Misch)
> Reduce need to rebuild indexes for various ALTER TABLE operations
> (Noah Misch) DUPLICATE?
> Avoid index rebuilds for no-rewrite ALTER TABLE / ALTER TYPE (Noah Misch)

Agreed, duplicates removed.

> This feature wasn't committed at all:
> Parallel pg_dump (Robert Haas, Joachim Wieland) DETAILS?

I was confused because there were infrastructure commits menting the
feature, so I thought it was lost somehow.

> Yes, this is still true:
> This is currently unused. STILL TRUE?

OK, fixed.

The attached patch includes all these fixes.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +