Re: pgsql: 9.3 release notes: move compatibility items into their own sect - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: 9.3 release notes: move compatibility items into their own sect
Date
Msg-id 20130504143306.GC5631@momjian.us
Whole thread Raw
In response to Re: pgsql: 9.3 release notes: move compatibility items into their own sect  (Peter Geoghegan <pg@heroku.com>)
List pgsql-committers
On Fri, May  3, 2013 at 09:39:38PM -0700, Peter Geoghegan wrote:
> On Fri, May 3, 2013 at 6:11 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > 9.3 release notes:  move compatibility items into their own section
>
> The commit_delay improvements should stay under performance, where I
> previously indicated they should be - it's clearly a notable new
> feature (commit_delay is way more effective now), as opposed to a
> tweak to the semantics of an existing feature. The fact that the
> behavior was changed could be separately noted, alongside the fact
> that Simon made commit_delay PGC_POSTMASTER (this is already
> separately noted anyway).
>
> Similarly, I think that this is a new feature that needs a separate
> compatibility note:
>
> Allow in-memory sorts to use their full memory allocation (Jeff Janes)
>
> It's possible that people were previously over-allocating memory to
> compensate for the server's former unwillingness to make full use of
> work_mem. You should specifically warn against that.

OK, I moved commit_delay back to performance, and moved in-memory sorts
up to compatibility.

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

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


pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: pgsql: 9.3 release notes: move compatibility items into their own sect
Next
From: Bruce Momjian
Date:
Subject: pgsql: 9.3 release notes: adjustments