Re: archive command doesnt work - Mailing list pgsql-general

From Laurenz Albe
Subject Re: archive command doesnt work
Date
Msg-id a3a4da91f3aa47d9e47802d8b274effab85202e3.camel@cybertec.at
Whole thread Raw
In response to Re: archive command doesnt work  (Alpaslan AKDAĞ <alpaslanakdag@gmail.com>)
Responses Re: archive command doesnt work  (Mateusz Henicz <mateuszhenicz@gmail.com>)
Re: archive command doesnt work  (Alpaslan AKDAĞ <alpaslanakdag@gmail.com>)
List pgsql-general
On Thu, 2024-02-08 at 09:23 +0100, Alpaslan AKDAĞ wrote:
> Thank you for your answer.
>
> I have checked the pg_is_in_recovery() and here are the results
> from primary and hot stand by server.
>
> Primary (old standby ):
> select pg_is_in_recovery();
>  pg_is_in_recovery
> -------------------
>  f
> (1 row)
>
> hot standby(old primary):
> select pg_is_in_recovery();
>  pg_is_in_recovery
> -------------------
>  t
> (1 row)
> and there is also standby.signal file in standby server.
> So it seems that there is nothing wrong.
>
> recovery_min_apply_delay = '2d' are set in warm standby servers.
> Before the switchover we had the same settings but we did not have this problem.

It is becoming increasingly obvious that you never actually performed
a switchover: it seems that you didn't promote the standby.

Either use

  pg_ctl promote -D /path/to/datadir

on the command line or

  SELECT pg_promote();

in SQL.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: veem v
Date:
Subject: Re: Partitioning options
Next
From: Mateusz Henicz
Date:
Subject: Re: archive command doesnt work