> On 23 Sep 2026, at 5:51 PM, Jonathan S. Katz <[email protected]> wrote:
>
> 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
>
> <v4-doc-release-19-major.diff>
Hi,
Would it be worth mentioning the new jsonpath string methods in the release
highlights? (My patch —> biased)
The overview currently focuses mostly on operational and performance
improvements, and this could provide a useful application-developer-facing
addition.
Its value is in how the methods compose: trimming whitespace, normalizing case,
replacing text, and extracting string components directly within JSON path
expressions.
This makes common JSON querying and data-cleaning tasks easier to express
without moving those operations into surrounding SQL.
Also note that 18 itself was thin on JSON improvements it
Possible wording: “Expanded SQL/JSON path support with string methods for text
normalization and extraction, enabling more expressive JSON queries.”
