pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonathan S. Katz <jkatz@postgresql.org>
To: Thomas Munro <thomas.munro@gmail.com>
To: 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>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: pg15b3: recovery fails with wal prefetch enabled
Date: Mon, 5 Sep 2022 21:45:48 -0400
Message-ID: <7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org> (raw)
In-Reply-To: <CA+hUKGJxUy9EW-vkiqN_iYO5TFEJfijSwLrQCdHCB8KkVVWmgw@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>

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


Attachments:

  OpenPGP_signature (application/pgp-signature, 839B) download

view thread (25+ messages)  latest in thread

Message-ID: <7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org>
Permalink:  ../7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org/
Also on:    postgresql.org/message-id/7b52105d-b1ae-1c51-1794-2280e7c8cf06@postgresql.org

 · 

reply

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, 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, tgl@sss.pgh.pa.us
  Subject: Re: pg15b3: recovery fails with wal prefetch enabled
  In-Reply-To: <7b52105d-b1ae-1c51-1794-2280e7c8cf06@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