Re: pgsql: Generic Messages for Logical Decoding - Mailing list pgsql-committers

From Andres Freund
Subject Re: pgsql: Generic Messages for Logical Decoding
Date
Msg-id 20160407044728.afbjel7rihbkq3f6@alap3.anarazel.de
Whole thread Raw
In response to Re: pgsql: Generic Messages for Logical Decoding  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: pgsql: Generic Messages for Logical Decoding  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-committers
On 2016-04-07 12:26:28 +0900, Fujii Masao wrote:
> In my example, the WAL record of INSERT that I executed last should be in
> 000000010000000000000005. But pg_xlogdump could not display that.
> The output of pg_xlogdump was:
>
> $ pg_xlogdump data/pg_xlog/000000010000000000000005
> pg_xlogdump: FATAL:  could not find a valid record after 0/5000000
>
> ISTM that if a WAL file starts with the latter half of LOGICAL MESSAGE
> WAL data, pg_xlogdump treats it as invalid and gives up dumping the
> remaining WAL data in the file.

That'd obviously be something to investigate. IIRC there's a thread
nearby about something like this. But just to confirm, if you use -s
over multiple records it works?

Greetings,

Andres Freund


pgsql-committers by date:

Previous
From: Noah Misch
Date:
Subject: pgsql: Remove redundant message in AddUserToTokenDacl().
Next
From: Simon Riggs
Date:
Subject: pgsql: Load FK defs into relcache for use by planner