Re: pg15b3: recovery fails with wal prefetch enabled - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: pg15b3: recovery fails with wal prefetch enabled
Date
Msg-id 7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org
Whole thread Raw
In response to Re: pg15b3: recovery fails with wal prefetch enabled  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: pg15b3: recovery fails with wal prefetch enabled
List pgsql-hackers
On 9/5/22 7:18 PM, Thomas Munro wrote:
> On Mon, Sep 5, 2022 at 9:08 PM Thomas Munro <thomas.munro@gmail.com> wrote:
>>> At Mon, 05 Sep 2022 14:15:27 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in
>>> At Mon, 5 Sep 2022 16:54:07 +1200, Thomas Munro <thomas.munro@gmail.com> wrote in
>>>> On reflection, it'd be better not to clobber any pre-existing error
>>>> there, but report one only if there isn't one already queued.  I've
>>>> done that in this version, which I'm planning to do a bit more testing
>>>> on and commit soonish if there are no comments/objections, especially
>>>> for that part.
> 
> Well I was about to commit this, but beta4 just got stamped (but not
> yet tagged).  I see now that Jonathan (with RMT hat on, CC'd) meant
> commits should be in by the *start* of the 5th AoE, not the end.  So
> the procedural/RMT question is whether it's still possible to close
> this item in beta4.

Presumably because Tom stamped it, the released is wrapped so it 
wouldn't make Beta 4, but I defer to him to see if it can be included 
with the tag.

That said, if it doesn't make it for Beta 4, it would be in the next 
release (which is hopefully RC1).

Thanks,

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)
Next
From: Tom Lane
Date:
Subject: Re: pg15b3: recovery fails with wal prefetch enabled