Re: Remove page-read callback from XLogReaderState. - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Remove page-read callback from XLogReaderState.
Date
Msg-id CA+hUKGJ7ecf2xGVOwFBzk1gJzm82gAj6rw0LrMtgoaS7_D5-aA@mail.gmail.com
Whole thread Raw
In response to Re: Remove page-read callback from XLogReaderState.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Remove page-read callback from XLogReaderState.
List pgsql-hackers
On Wed, Apr 7, 2021 at 11:18 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> BTRW it's funny that after these patches, "xlogreader" no longer reads
> anything.  It's more an "xlog interpreter" -- the piece of code that
> splits individual WAL records from a stream of WAL bytes that's caller's
> responsibility to obtain somehow.  But (and, again, I haven't read this
> patch recently) it still offers pieces that support a reader, in
> addition to its main interface as the interpreter.  Maybe it's not a
> totally stupid idea to split it in even more different files.

Yeah, I like "decoder", and it's already called that in some places...



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ModifyTable overheads in generic plans
Next
From: Alvaro Herrera
Date:
Subject: Re: Remove page-read callback from XLogReaderState.