Re: Replication failed

From: Rambabu V <ram(dot)wissen(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Sreejith P <sreejith(at)lifetrenz(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Replication failed
Date: 2020-12-21 02:16:02
Message-ID: CADtiZxo_rQDTMX0iHhFutihjs=Q2UOAcgdGYisfT9B+hQCD6Dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Laurenz,

please let us know how to apply the patch, we are able to see below
attachments , once downloaded how to apply this patch.

AttachmentContent-TypeSize
repro_helper.patch
<https://www.postgresql.org/message-id/attachment/106141/repro_helper.patch>
application/octet-stream 1.3 KB
ready_file_fix.patch
<https://www.postgresql.org/message-id/attachment/106142/ready_file_fix.patch>
application/octet-stream

On Fri, Dec 18, 2020 at 2:13 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> 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
>
>
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2020-12-21 03:50:02 Re: Replication failed
Previous Message Stephen Frost 2020-12-18 17:54:39 Re: Grant request