Re: archive command doesnt work

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Alpaslan AKDAĞ <alpaslanakdag(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: archive command doesnt work
Date: 2024-02-08 20:10:26
Message-ID: a3a4da91f3aa47d9e47802d8b274effab85202e3.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mateusz Henicz 2024-02-08 20:24:36 Re: archive command doesnt work
Previous Message veem v 2024-02-08 19:43:00 Re: Partitioning options