| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| 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:59:43 |
| Message-ID: | 4967908F.8070902@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Aidan Van Dyk wrote:
> * 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.
I thought that only applied when the filesystem page-size was less than
the data we were writing?
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reg Me Please | 2009-01-09 18:06:27 | [EXPLAIN] Nested loops |
| Previous Message | Bruce Momjian | 2009-01-09 17:44:33 | Re: Improving compressibility of WAL files |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-09 18:22:43 | Re: Improving compressibility of WAL files |
| Previous Message | Bruce Momjian | 2009-01-09 17:44:33 | Re: Improving compressibility of WAL files |