Re: [REVIEW] Re: Compression of full-page-writes

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "Rahila Syed" <rahilasyed(dot)90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [REVIEW] Re: Compression of full-page-writes
Date: 2014-09-29 15:27:01
Message-ID: 54297A45.8080904@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/29/2014 06:02 PM, Robert Haas wrote:
> On Mon, Sep 29, 2014 at 8:36 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> 1) I don't think it's a good idea to put the full page write compression
>> into struct XLogRecord.
>
> Why not, and where should that be put?

It should be a flag in BkpBlock.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2014-09-29 15:28:20 Re: json (b) and null fields
Previous Message Andres Freund 2014-09-29 15:20:48 Re: [REVIEW] Re: Compression of full-page-writes