Re: Compression of full-page-writes

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Rahila Syed <rahilasyed90(at)gmail(dot)com>
Cc: Rahila Syed <rahilasyed(dot)90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compression of full-page-writes
Date: 2014-06-11 01:05:18
Message-ID: CAB7nPqTp5QAGtNR5rXFhsHMjQanrQVKs4eLged+9w46qUENNrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 10, 2014 at 11:49 PM, Rahila Syed <rahilasyed90(at)gmail(dot)com> wrote:
> Hello ,
>
>
> In order to facilitate changing of compression algorithms and to be able to
> recover using WAL records compressed with different compression algorithms,
> information about compression algorithm can be stored in WAL record.
>
> XLOG record header has 2 to 4 padding bytes in order to align the WAL
> record. This space can be used for a new flag in order to store information
> about the compression algorithm used. Like the xl_info field of XlogRecord
> struct, 8 bits flag can be constructed with the lower 4 bits of the flag
> used to indicate which backup block is compressed out of 0,1,2,3. Higher
> four bits can be used to indicate state of compression i.e
> off,lz4,snappy,pglz.
>
> The flag can be extended to incorporate more compression algorithms added in
> future if any.
>
> What is your opinion on this?
-1 for any additional bytes in WAL record to control such things,
having one single compression that we know performs well and relying
on it makes the life of user and developer easier.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-06-11 01:42:42 Re: branch for 9.5?
Previous Message Tom Lane 2014-06-11 00:39:32 Re: "RETURNING PRIMARY KEY" syntax extension