pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jerry Sievers <gsievers19@comcast.net>
To: Dhirendra Singh <dhirendraks@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: standby server is complaining about missing wal file after switchover
Date: Thu, 13 Oct 2022 18:42:42 -0500
Message-ID: <m01qrbnvd9.fsf@comcast.net> (raw)
In-Reply-To: <CAEyh4sZtxm=f-BiakMy83WgEY8_woAb61EY0Jpc=61COKrLj8Q@mail.gmail.com>
References: <CAEyh4sZtxm=f-BiakMy83WgEY8_woAb61EY0Jpc=61COKrLj8Q@mail.gmail.com>

Dhirendra Singh <dhirendraks@gmail.com> writes:

> Hi,
> My postgres version is 14.2
> I have setup streaming replication between a primary and a standby using replication slot and without
> archive.
> I have created replication slot "slot1" on the primary.
> I did switchover following below steps.
> 1. shutdown the primary server.
> 2. created replicated slot "slot1" on standby and promoted it to primary.
> 3. run pg_rewind on the old primary and made it standby.
> 4. started the old primary as new standby.
>
> I got following error in the new standby. it is complaining about missing wal file on the new primary.
>
> 2022-10-13 12:58:48.497 UTC [25] LOG:  fetching timeline history file for timeline 2 from primary
> server
> 2022-10-13 12:58:48.508 UTC [25] LOG:  started streaming WAL from primary at 0/B000000 on
> timeline 1
> 2022-10-13 12:58:48.508 UTC [25] FATAL:  could not receive data from WAL stream: ERROR: 
> requested WAL segment 00000002000000000000000B has already been removed
> 2022-10-13 12:58:48.509 UTC [21] LOG:  new target timeline is 2
> 2022-10-13 12:58:48.580 UTC [28] LOG:  started streaming WAL from primary at 0/B000000 on
> timeline 2
> 2022-10-13 12:58:48.580 UTC [28] FATAL:  could not receive data from WAL stream: ERROR: 
> requested WAL segment 00000002000000000000000B has already been removed
>
> why the new primary has removed the wal file even though i created replication slot on it before
> promoting.
> value of max_slot_wal_keep_size is -1 and wal_keep_size is 0

Dunno but did you call the pg_create_physical_replication_slot()
 function with arg2=true to have it immediately keep the WAL pointer?

I believe otherwise not until the slot has been connected to does it
retain anything.

HTH

>
> Thanks,
> Dhirendra.





view thread (3+ messages)  latest in thread

Message-ID: <m01qrbnvd9.fsf@comcast.net>
Permalink:  ../m01qrbnvd9.fsf@comcast.net/
Also on:    postgresql.org/message-id/m01qrbnvd9.fsf@comcast.net

 · 

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-admin@postgresql.org
  Cc: gsievers19@comcast.net, dhirendraks@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: standby server is complaining about missing wal file after switchover
  In-Reply-To: <m01qrbnvd9.fsf@comcast.net>

* 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