Re: General support on postgres replication

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Vijaykumar Patil <vijaykumar(dot)patil(at)maersk(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: General support on postgres replication
Date: 2023-11-23 08:43:48
Message-ID: 5f0a9def7fddf4cfca1d6ea2af141da633b97d37.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2023-11-22 at 08:57 +0000, Vijaykumar Patil wrote:
> I have created streaming replication with two nodes .
>  
> One is primary and 2nd one is standby but after doing any DML or DDL operation on
> primary Walreceiver process is terminated on standby and standby database is
> opening in read write mode.
>  
> Below are the error details .
>  
> 2023-11-22 03:39:58 EST [1275942]: user=,db=,app=,client=LOG:  recovery stopping before commit of transaction 25627, time 2023-11-22 03:39:58.013764-05
> 2023-11-22 03:39:58 EST [1275942]: user=,db=,app=,client=LOG:  redo done at 1/260059E0 system usage: CPU: user: 0.02 s, system: 0.04 s, elapsed: 5197.90 s
> 2023-11-22 03:39:58 EST [1276846]: user=,db=,app=,client=FATAL:  terminating walreceiver process due to administrator command
> ERROR: [037]: archive-get command requires option: pg1-path
>        HINT: does this stanza exist?

It looks like you have a bad "restore_command" configured.

It would be intereseting to see the log lines before the ones you are showing.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2023-11-23 08:48:14 Re: Configuration knobs & dials to speed up query optimization
Previous Message Laurenz Albe 2023-11-23 08:40:28 Re: strange behavior of pg_hba.conf file