Re: Replication failed

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Sreejith P <sreejith(at)lifetrenz(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Replication failed
Date: 2020-12-18 11:55:34
Message-ID: ac62a1ce2074aff1f4161d30fbbd12b8fe8a1bf5.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> > 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
>
> There was a crash.
>
> Master recovered automatically .. But replication failed.

Then I am pretty sure that this is the same problem.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2020-12-18 12:07:21 User granted all access to schema, but can't see tables
Previous Message Sreejith P 2020-12-18 10:19:02 Re: Replication failed