Re: pgsql: Reorder 9.3 release note items

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Reorder 9.3 release note items
Date: 2013-04-21 15:52:14
Message-ID: CAM3SWZRYCwddewcFe9HztMU3cBB_wi6Vm_SCMaVh9KR-oxXcHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, Apr 21, 2013 at 12:57 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> * Improve memory usage for in-memory sorts - IMHO this should read
> "Allow in-memory sorts to use their full memory allocation", which
> then explains why users may see higher memory usage and why they
> should think about altering settings

+1. As I believe you pointed out at the time of the development of
this feature, it has the potential to greatly increase the amount of
memory allocated by tuplesort, but only within the actual bounds
specified by the DBA. There needs to be a clear warning of that - it's
easy to imagine that DBAs are specifying a high value of work_mem to
compensate for the previous implementation's tendency to under
provision.

> * "Require superuser privileges to set commit_delay"
> Meaning of commit_delay has changed and users should review their
> settings, if used

+1

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2013-04-21 19:22:38 Re: pgsql: Reorder 9.3 release note items
Previous Message Bruce Momjian 2013-04-21 14:09:14 Re: pgsql: Reorder 9.3 release note items