From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Sreejith P <sreejith@lifetrenz.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Replication failed
Date: Fri, 18 Dec 2020 09:43:30 +0100
Message-ID: <9492f3e4fff86b6fcb1d064d680920e8579d9c37.camel@cybertec.at> (raw)
In-Reply-To: <E73F4CFB-E322-461E-B1EC-82FAA808FEE6@lifetrenz.com>
References: <E73F4CFB-E322-461E-B1EC-82FAA808FEE6@lifetrenz.com>
On Fri, 2020-12-18 at 00:56 +0530, Sreejith P wrote:
> We had 1 M x 4 slave server streaming replication using Postgres 10. Was working successfully for long time.
>
> Suddenly all replication servers got failed and getting following message.
>
> 2020-12-17 22:24:32 +04 [1587]: [357-1] db=,user=LOG: invalid contrecord length 2722 at AEA/A1FFF9E0.
>
> Requesting help for identifying root cause.
Looks like this problem:
https://postgr.es/m/77734732-44A4-4209-8C2F-3AF36C9D4D18%40amazon.com
Was there a crash on the primary sever?
There is a patch under development at this thread:
https://postgr.es/m/CBDDFA01-6E40-46BB-9F98-9340F4379505%40amazon.com
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, sreejith@lifetrenz.com, pgsql-admin@lists.postgresql.org
Subject: Re: Replication failed
In-Reply-To: <9492f3e4fff86b6fcb1d064d680920e8579d9c37.camel@cybertec.at>
* 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