Re: New 9.6 external sort guidance around temp_tablespaces and maintenance_work_mem

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New 9.6 external sort guidance around temp_tablespaces and maintenance_work_mem
Date: 2016-04-30 23:39:22
Message-ID: CAM3SWZQU1jqQBvNEdwcK73wjvpFyGRb054XKkueomxo8Du+eQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 30, 2016 at 4:26 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Sat, Apr 30, 2016 at 04:23:00PM -0700, Peter Geoghegan wrote:
>> Maybe there is a place to emphasize this change in the release notes.
>> I don't really want to make it about the external sort feature,
>> though, because enabling higher work_mem settings by making sure that
>> does not disadvantage external sorts is as much about enabling
>> HashAggregates as it is about enabling internal sorts.
>
> We do often mention in the release notes areas that will need retuning.

How do you feel about it in this instance?

As you may have gathered, my perspective is that the external sorting
patches were more about fixing a problem with tuplesort than about
improving its performance. The performance characteristics of the old
approach to sorting runs were all over the place, which made
increasing work_mem like taking one step forward, then two steps
backwards.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-04-30 23:41:33 Re: New 9.6 external sort guidance around temp_tablespaces and maintenance_work_mem
Previous Message Bruce Momjian 2016-04-30 23:26:09 Re: New 9.6 external sort guidance around temp_tablespaces and maintenance_work_mem