Re: [PATCHES] Full page writes improvement, code update - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: [PATCHES] Full page writes improvement, code update
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901E7B246@m0143.s-mxs.net
Whole thread Raw
In response to Re: [PATCHES] Full page writes improvement, code update  (Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>)
Responses Re: [PATCHES] Full page writes improvement, code update  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
> Without a switch, because both full page writes and
> corresponding logical log is included in WAL, this will
> increase WAL size slightly
> (maybe about five percent or so).   If everybody is happy
> with this, we
> don't need a switch.

Sorry, I still don't understand that. What is the "corresponding logical
log" ?
It seems to me, that a full page WAL record has enough info to produce a

dummy LSN WAL entry. So insead of just cutting the full page wal record
you
could replace it with a LSN WAL entry when archiving the log.

Then all that is needed is the one flag, no extra space ?

Andreas


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: Crash bug in 8.2.3 on Solaris 10/Sparc
Next
From: Heikki Linnakangas
Date:
Subject: Re: Autovacuum vs statement_timeout