From: Jonathan S. Katz <jkatz@postgresql.org>
To: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: David Steele <david@pgmasters.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg15b3: recovery fails with wal prefetch enabled
Date: Tue, 6 Sep 2022 09:55:52 -0400
Message-ID: <3f2c09a6-0b7d-7004-3356-b2f3f520f3ce@postgresql.org> (raw)
In-Reply-To: <CA+hUKG+nHCSx3vqYD8HUGhEoEmKqKTHtymQw9-EVXmCn39gFmQ@mail.gmail.com>
References: <CA+hUKGLYYaXWQfoEgPLsQ-6DwpEUZzbh6g_xhfF+yN=jTHC1mw@mail.gmail.com>
<CA+hUKGL=+0nF8o8xG5DDUepG0ZxgDXusF=Jqtd7FmtFvmR1Gmg@mail.gmail.com>
<CA+hUKGJXfQJHs2jmVOoOo2J12-6m36E0ytDiyrqp-EvFwupvew@mail.gmail.com>
<20220905.143436.1254379754225361598.horikyota.ntt@gmail.com>
<CA+hUKG+vsm00hYtwSyQX9T2cw3qX_d6ZDgAtT9Z+4reO4ePt8A@mail.gmail.com>
<CA+hUKGJxUy9EW-vkiqN_iYO5TFEJfijSwLrQCdHCB8KkVVWmgw@mail.gmail.com>
<7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org>
<3012983.1662429098@sss.pgh.pa.us>
<CA+hUKG+nHCSx3vqYD8HUGhEoEmKqKTHtymQw9-EVXmCn39gFmQ@mail.gmail.com>
On 9/5/22 10:03 PM, Thomas Munro wrote:
> 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.
To close this loop, I added a section for "fixed before RC1" to Open
Items since this is presumably the next release. We can include it there
once committed.
Jonathan
Attachments:
OpenPGP_signature (application/pgp-signature, 839B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jkatz@postgresql.org, thomas.munro@gmail.com, tgl@sss.pgh.pa.us, horikyota.ntt@gmail.com, pryzby@telsasoft.com, noriyoshi.shinoda@hpe.com, tomas.vondra@enterprisedb.com, sfrost@snowman.net, andres@anarazel.de, alvherre@2ndquadrant.com, tomas.vondra@2ndquadrant.com, 9erthalion6@gmail.com, david@pgmasters.net
Subject: Re: pg15b3: recovery fails with wal prefetch enabled
In-Reply-To: <3f2c09a6-0b7d-7004-3356-b2f3f520f3ce@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox