Re: pg15b3: recovery fails with wal prefetch enabled
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, "Shinoda, Noriyoshi (PN Japan FSIP)" <noriyoshi.shinoda@hpe.com>,
Tomas Vondra <tomas.vondra@enterprisedb.com>, Stephen Frost <sfrost@snowman.net>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@2ndquadrant.com>,
Tomas Vondra <tomas.vondra@2ndquadrant.com>, Dmitry Dolgov <9erthalion6@gmail.com>, David Steele <david@pgmasters.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-09-06T02:03:52Z
Lists: pgsql-hackers
On Tue, Sep 6, 2022 at 1:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > "Jonathan S. Katz" <jkatz@postgresql.org> writes: > > On 9/5/22 7:18 PM, Thomas Munro wrote: > >> 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. > > I already made the tarballs available to packagers, so adding this > would involve a re-wrap and great confusion. In any case, I'm not > a fan of pushing fixes within a day or two of the wrap deadline, > let alone after it; you get inadequate buildfarm coverage when you > cut corners that way. I think this one missed the boat. Got it. Yeah I knew it was going to be a close thing with a problem diagnosed on Thursday/Friday before a Monday wrap, even before I managed to confuse myself about dates and times. Thanks both.
Commits
-
Fix recovery_prefetch with low maintenance_io_concurrency.
- adb466150b44 16.0 landed
- dd38ff28addc 15.0 landed
-
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
- a2039b1f8e90 15.0 cited