| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Full page writes improvement, code update |
| Date: | 2007-03-30 08:22:23 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57901E7B246@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2007-03-30 08:40:08 | Multibyte LIKE optimization |
| Previous Message | Zdenek Kotala | 2007-03-30 07:16:30 | Re: Crash bug in 8.2.3 on Solaris 10/Sparc |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2007-03-30 08:40:08 | Multibyte LIKE optimization |
| Previous Message | NikhilS | 2007-03-30 06:58:02 | Auto Partitioning Patch - WIP version 1 |