Re: Default setting for enable_hashagg_disk - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id CA+TgmoYq2Jfqfs09cTmwbv0eHcj0c5hrDL8wiiFZYOWp3uL+oA@mail.gmail.com
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: Default setting for enable_hashagg_disk  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Mon, Jun 22, 2020 at 11:06 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> This was addressed in 92c58fd94801dd5c81ee20e26c5bb71ad64552a8
> https://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=34994&oldid=34993

I mean, that's fine, but I am trying to make a more general point
about priorities. Getting the GUCs right is a lot less important than
getting the feature right.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: suggest to rename enable_incrementalsort
Next
From: Fujii Masao
Date:
Subject: Assertion failure in pg_copy_logical_replication_slot()