From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Kyle Cordes" <kyle(at)kylecordes(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Improving compressibility of WAL files |
Date: | 2009-01-08 23:24:28 |
Message-ID: | 496636CC.EE98.0025.0@wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
>>> Aidan Van Dyk <aidan(at)highrise(dot)ca> 01/08/09 5:02 PM >>>
> *I* would really like this wal zero'ing...
pg_clearxlogtail (in pgfoundry) does exactly the same zeroing of the
tail as a filter. If you pipe through it on the way to gzip, there
is no increase in disk I/O over a straight gzip, and often an I/O
savings. Benchmarks of the final version showed no measurable
performance cost, even with full WAL files.
It's not as convenient to use as what your patch does, but it's not
all that hard either. There is also pglesslog, although we had
pg_clearxlogtail working before we found the other, so we've never
checked it out. Perhaps it does even better.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2009-01-08 23:29:08 | Re: Improving compressibility of WAL files |
Previous Message | Jeremiah Jahn | 2009-01-08 23:10:53 | Thanx for 8.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2009-01-08 23:29:08 | Re: Improving compressibility of WAL files |
Previous Message | Aidan Van Dyk | 2009-01-08 23:02:35 | Re: Improving compressibility of WAL files |