| From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Greg Smith <gsmith(at)gregsmith(dot)com>, Hannu Krosing <hannu(at)krosing(dot)net>, Kyle Cordes <kyle(at)kylecordes(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improving compressibility of WAL files |
| Date: | 2009-01-09 17:29:38 |
| Message-ID: | 20090109172938.GM12094@yugib.highrise.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
* Richard Huxton <dev(at)archonet(dot)com> [090109 12:22]:
> > Yeah: the archiver process doesn't have that information available.
> Am I being really dim here - why isn't the first record in the WAL file
> a fixed-length record containing e.g. txid_start, time_start, txid_end,
> time_end, length? Write it once when you start using the file and once
> when it's finished.
It would break the WAL "write-block/sync-block" forward only progress of
the xlog, which avoids the whole torn-page problem that the heap has.
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-09 17:44:33 | Re: Improving compressibility of WAL files |
| Previous Message | Richard Broersma | 2009-01-09 17:24:06 | Re: Seeking PG Booth Volunteers for 2009 SCALE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-09 17:34:01 | Re: Hot standby, RestoreBkpBlocks and cleanup locks |
| Previous Message | Jeff Davis | 2009-01-09 17:25:50 | Re: Visibility map and freezing |