Re: intercepting WAL writes - Mailing list pgsql-hackers

From Mike
Subject Re: intercepting WAL writes
Date
Msg-id 009001c8c12d$efd67ec0$cf837c40$@com
Whole thread Raw
In response to Re: intercepting WAL writes  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: intercepting WAL writes  ("Koichi Suzuki" <koichi.szk@gmail.com>)
Re: intercepting WAL writes  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Wed, May 28, 2008 at 8:30 PM, Mike <mike@fonolo.com> wrote:
>> When you say a bit of decoding, is that because the data written to the
logs
>> is after the query parser/planner? Or because it's written in several
>> chunks? Or?
>
>Because that's the actual recovery record.  There is no SQL text, just
>the WAL record type (XLOG_HEAP_INSERT, XLOG_HEAP_UPDATE,
>XLOG_XACT_COMMIT, ...) and the data as it relates to that operation.

Oh- right- that makes sense.

I installed and started looking at the source code for xlogviewer and
xlogdump; seems like a reasonable place to start.

Thanks for your help,

Mike



pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Catching exceptions from COPY
Next
From: "Jignesh K. Shah"
Date:
Subject: Re: [JDBC] Re: How embarrassing: optimization of a one-shot query doesn't work