Re: standby recovery fails (tablespace related) (tentative patch and discussion)

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: thomas(dot)munro(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, boekewurm+postgres(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Date: 2022-07-29 10:59:03
Message-ID: 20220729105903.xuiw23kpcdphcvel@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Jul-29, Kyotaro Horiguchi wrote:

> At Fri, 29 Jul 2022 11:27:01 +1200, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote in
> > Maybe it just needs a replication slot? I see:
> >
> > ERROR: requested WAL segment 000000010000000000000003 has already been removed
>
> Agreed, I see the same. The same failure can be surely reproducible
> by inserting wal-switch+checkpoint after taking backup [1]. And it is
> fixed by the attached.

WFM, pushed that way. I added a slot drop after the pg_stat_replication
count check to be a little less intrusive. Thanks Matthias for
reporting. (Note that the Cirrus page has a download link for the
complete logs as artifacts).

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more right than other times."
(Linus Torvalds)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-07-29 12:22:26 Re: generic plans and "initial" pruning
Previous Message Mats Kindahl 2022-07-29 10:36:13 Re: Table AM and DROP TABLE [ Was: Table AM and DDLs]