And you will have a chance to encounter full page writes, whole page image, which could be produced during the hot backup and the first modification to the data page after a checkpoint (if you turn full page write option "on" by GUC).
2008/5/29 Mike <[EMAIL PROTECTED]>: > On Wed, May 28, 2008 at 8:30 PM, Mike <[EMAIL PROTECTED]> 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 > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- ------ Koichi Suzuki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
