Skip site navigation (1) Skip section navigation (2)

Re: Quick-and-dirty compression for WAL backup blocks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Quick-and-dirty compression for WAL backup blocks
Date: 2005-06-01 14:12:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> writes:
> I also noticed your comment above that mentioned that compression would be
> less effective as the pages became more full. Would changing the loading
> factor of database pages have an effect here, as I would have thought that
> the WAL would be fsync'd more aggressively than the heap?

Yeah, it's predictable that leaving more free space per page would make
the optimization more effective.  I don't have anything quantitative to
say about it.

> If you do manage to go ahead with the code, I'd be very interested to see
> some comparisons in bytes written to XLog for old and new approaches for
> some inserts/updates. Perhaps we could ask Mark to run another TPC benchmark
> at OSDL when this and the CRC changes have been completed.

Good idea.  One point is that the larger the checkpoint interval, the
less this matters at all, because a backup block is only written for
a given page the first time it is modified after a checkpoint.  (This
is one of the big reasons frequent checkpoints are expensive.)  IIRC
Mark was using unrealistically large checkpoint intervals, which would
mean he'd underestimate the effects of optimizing backup blocks.

			regards, tom lane


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-06-01 14:14:42
Subject: Re: NOLOGGING option, or ?
Previous:From: Bruce MomjianDate: 2005-06-01 14:12:18
Subject: Re: NOLOGGING option, or ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group