| 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-30 02:55:28 |
| Message-ID: | CAH2-Wzmp7OX9pdGrPfYWUYx01e6ys_critRTwwRECAU=o=rgLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 29, 2020 at 7:48 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Well, that seems to be repeating what is already in the docs for
> hash_mem_multiplier, which I try to avoid. One other direction is to
> put something in the incompatibilities section. Does that make sense?
I would prefer to put it next to the hash agg item itself. It's more
likely to be noticed there, and highlighting it a little seems
warranted.
OTOH, this may not be a problem at all for many individual users.
Framing it as a tip rather than a compatibility item gets that across.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-07-30 03:24:33 | Re: [PATCH] Tab completion for VACUUM of partitioned tables |
| Previous Message | Bruce Momjian | 2020-07-30 02:48:32 | Re: PG 13 release notes, first draft |