| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Banck <mbanck(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add list of major features to the v19 release notes |
| Date: | 2026-09-23 14:51:31 |
| Message-ID: | 41ef3063-25fe-43a4-b8d9-cd715593665f@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/18/26 11:52 AM, Nathan Bossart wrote:
> Thanks for the patch.
Thanks for the review - sorry for the delay, for some reason this didn't
hit my inbox.
> nit: extra space before "command"
Fixed.
> s/which can help increase/which can improve
Accepted.
> nit: extra "and"
Fixed.
> Hm. Can we be more descriptive here? Maybe something like "Support for
> read-your-writes query patterns on standbys via the new..."
Doing some research, it seems the most common word is "consistency". I
opted for that. LMK what you think.
> Per commits 1a562a2661b and e527bf17d04, I think we're just calling it
> "WAIT" and not "WAIT FOR".
Ack; I'll refrain from bikeshedding. Adjusted.
>> + <link linkend="autovacuum-priority">user-defined prioritization of autovacuuming</link>.
>
> IMHO this makes it sound like users will be able to choose the priority of
> each individual table, when we actually are just giving them a handful of
> coarse controls. I think we ought to emphasize the scoring system instead.
> In theory, most users shouldn't need to adjust anything and the
> prioritization will "Just Work" for them.
Ack; I took a read of the docs and saw we were referring to it as
autovacuuming prioritization, so tried:
+ <link linkend="autovacuum-priority">autovacuuming prioritization</link>
+ through a new scoring system.
if you think that makes sense based on that. Patch attached.
Thanks,
Jonathan
| Attachment | Content-Type | Size |
|---|---|---|
| v4-doc-release-19-major.diff | text/plain | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2026-09-23 15:06:50 | Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten |
| Previous Message | Nathan Bossart | 2026-09-23 14:41:36 | Re: Speed up lpad() and rpad() for one-byte padding strings |