| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-07-29 22:34:22 |
| Message-ID: | CAH2-Wzn3kwQm_pe6g2=ki+P7+ZRqH5GvFGn6SWfv_j7UUgcLdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Bruce,
On Fri, Jun 26, 2020 at 3:24 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Patch attached and applied to PG 13.
I committed the hash_mem_multiplier GUC to Postgres 13 just now.
There should be a note about this in the Postgres 13 release notes,
for the usual reasons. More importantly, the "Allow hash aggregation
to use disk storage for large aggregation result sets" feature should
reference the new GUC directly. Users should be advised that the GUC
may be useful in cases where they upgrade and experience a performance
regression linked to slower hash aggregation. Just including a
documentation link for the GUC would be very helpful.
Thanks
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-07-29 23:44:26 | Re: [PATCH] Tab completion for VACUUM of partitioned tables |
| Previous Message | Thomas Munro | 2020-07-29 22:29:52 | Re: recovering from "found xmin ... from before relfrozenxid ..." |