Horton

Re: ALTER SYSTEM between upgrades

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL-documentation <pgsql-docs@postgresql.org>
Date: 2020-08-31T21:36:40Z
Lists: pgsql-hackers, pgsql-docs 
On Wed, Aug 26, 2020 at 12:22:25AM +0200, Daniel Gustafsson wrote:
> >> One can argue whether those bulletpoints are sufficient for stressing the
> >> importance, but it's at least mentioned.  There is however no mention of
> >> postgresql.auto.conf which clearly isn't helping anyone, so we should fix that.
> >> 
> >> Taking that a step further, maybe we should mention additional config files
> >> which could be included via include directives?  There are tools out there who
> >> avoid changing the users postgresql.conf by injecting an include directive
> >> instead; they might've placed the included file alongside postgresql.conf.
> > 
> > I have developed the attached pg_upgrade doc patch to address this.
> 
> LGTM, thanks!

Patch applied,

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

  The usefulness of a cup is in its emptiness, Bruce Lee

Commits

  1. Add hash_mem_multiplier GUC.

  2. HashAgg: use better cardinality estimate for recursive spilling.

  3. Remove hashagg_avoid_disk_plan GUC.

  4. Doc fixup for hashagg_avoid_disk_plan GUC.

  5. Rework HashAgg GUCs.

  6. Disk-based Hash Aggregation.

  7. Implement partition-wise grouping/aggregation.

  8. Defer creation of partially-grouped relation until it's needed.