Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Aleš Zelený <zeleny(dot)ales(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208
Date: 2019-10-02 23:23:20
Message-ID: 26926.1570058600@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Aleš Zelený (zeleny(dot)ales(at)gmail(dot)com) wrote:
>> But recovery on replica failed to proceed WAL file
>> 0000000100000FED00000039 with log message: " invalid contrecord length
>> 1956 at FED/38FFE208".

> Err- you've drawn the wrong conclusion from that message (and you're
> certainly not alone- it's a terrible message and we should really have a
> HINT there or something).

Yeah, those messages are all pretty ancient, from when WAL was new and not
to be trusted much. Perhaps the thing to do is move the existing info
into DETAIL and make the primary message be something like "reached
apparent end of WAL stream".

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2019-10-02 23:24:02 Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208
Previous Message Adrian Klaver 2019-10-02 23:16:29 Re: performance of pg_upgrade "Copying user relation files"