Re: Quick-and-dirty compression for WAL backup blocks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Quick-and-dirty compression for WAL backup blocks
Date
Msg-id 4169.1118075085@sss.pgh.pa.us
Whole thread Raw
In response to Re: Quick-and-dirty compression for WAL backup blocks  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Quick-and-dirty compression for WAL backup blocks
List pgsql-hackers
Heikki Linnakangas <hlinnaka@iki.fi> writes:
> Vacuum doesn't zero out the free space between lower and upper,

It does now ;-)

> How about adding a flag to XLogRecData to indicate if the space between 
> pd_lower and pd_upper is meaningful or not? The XLogInsert caller probably 
> knows that. That way you could completely skip over the free space if 
> it's not meaningful, saving even more cycles.

Hmm ... that might not be a bad idea.  As far as I can think offhand,
all the XLogInsert callers know very well what type of page they are
working with, so they would always be able to set such a flag correctly.

Would this be institutionalizing a particular approach to data
compression in the XLogInsert API, though?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Quick-and-dirty compression for WAL backup blocks
Next
From: Bruce Momjian
Date:
Subject: Re: graphical representaion of the catalogue