From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Draft release notes for next week's releases are up |
Date: | 2024-08-03 15:14:20 |
Message-ID: | CAAKRu_YJJ_pRm3W4Ys8RW3EAg7AFEUwjE67-o6KwycFeDbpMJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 2, 2024 at 4:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> See
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ee219ee8c40d88e7a0ef52c3c1b76c90bbd0d164
>
> As usual, please send corrections/comments by Sunday.
For the "Prevent infinite loop in VACUUM" item, I noticed two things
1) In REL_17_STABLE, the behavior is an ERROR -- not an infinite loop.
Perhaps it is not worth mentioning the differing behavior because 17
hasn't GA'd yet, but I just wanted to bring this up since I wasn't
sure of the convention.
2) The note says <command>VACUUM</command>. This issue is, of course,
not limited to explicitly issued vacuum commands (i.e.
autovacuum-initiated vacuums can also encounter it). Again, I don't
know if this matters or what the convention is here.
- Melanie
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-08-03 15:20:13 | Re: Fix inappropriate uses of atol() |
Previous Message | David Rowley | 2024-08-03 14:11:18 | Re: Speed up JSON escape processing with SIMD plus other optimisations |