Re: pgsql: Generic Messages for Logical Decoding
От | Fujii Masao |
---|---|
Тема | Re: pgsql: Generic Messages for Logical Decoding |
Дата | |
Msg-id | CAHGQGwEo_GncJKTq1MrtCOiJL8cCP7xcgV8--m9OS32ELn8vuA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Generic Messages for Logical Decoding (Andres Freund <andres@anarazel.de>) |
Список | pgsql-committers |
On Thu, Apr 7, 2016 at 1:47 PM, Andres Freund <andres@anarazel.de> wrote: > 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. Okay, will check. Thanks for the info! > But just to confirm, if you use -s > over multiple records it works? Yeah, it worked expected. Regards, -- Fujii Masao
В списке pgsql-committers по дате отправления: