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

From Junji TERAMOTO
Subject Re: Quick-and-dirty compression for WAL backup blocks
Date
Msg-id 42A556CA.6030003@lab.ntt.co.jp
Whole thread Raw
In response to Re: Quick-and-dirty compression for WAL backup blocks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

>>>>In the XLogInsert(), it makes two kinds of logs, "whole buffer(page)
>>>>log" and "partial buffer log", isn't it?  Is it only "who buffer
>>>>log"
>>>>to generate a log with "hole"?
>
>>
>> Right.

I see.
I think, it is important to reduce the necessities to write whole pages
to WAL (as TODO list).
# It seems difficult to do so... Compressing WAL is easier way.

>> No, because the WAL code cannot assume that all pages follow the
>> convention that pd_lower and pd_upper represent the boundaries of
>> free space.  (As a counterexample: index metapages don't always
>> do that.)

Oh, I forget it.
And I think it is good idea to modify XLogInsert API as CVS, too.

-- 
Junji Teramoto


pgsql-hackers by date:

Previous
From: "Qingqing Zhou"
Date:
Subject: Re: adding new pages bulky way
Next
From: Atsushi Ogawa
Date:
Subject: Re: [PATCHES] regexp_replace