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

From: Junji TERAMOTO <teramoto(dot)junji(at)lab(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Quick-and-dirty compression for WAL backup blocks
Date: 2005-06-07 08:11:54
Message-ID: 42A556CA.6030003@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Phil Endecott 2005-06-07 11:16:19 Re: CPU-intensive autovacuuming
Previous Message Martin Pitt 2005-06-07 07:16:06 Re: libpq API incompatibility between 7.4 and 8.0