From: Chapman Flack <chap@anastigmatix.net>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: AdvanceXLInsertBuffer vs. WAL segment compressibility
Date: Mon, 25 Jul 2016 23:32:59 -0400
Message-ID: <5796D9EB.6070407@anastigmatix.net> (raw)
In-Reply-To: <CAB7nPqQ5NS5E-rWzd76MQHBEoc5cGHjSrUs4W6EiTxwWEx338Q@mail.gmail.com>
References: <579297F8.7020107@anastigmatix.net>
<CAA4eK1L7UvOS8TpUvoMuGZ4Mid=Mef-Cq5Q0M-2oYSHC-CSikw@mail.gmail.com>
<57962061.9010506@anastigmatix.net>
<CAB7nPqQ5NS5E-rWzd76MQHBEoc5cGHjSrUs4W6EiTxwWEx338Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 07/25/16 22:09, Michael Paquier wrote:
> This is over-complicating things for little gain. The new behavior of
> filling in with zeros the tail of a segment makes things far better
> when using gzip in archive_command.
Then how about filling with actual zeros, instead of with mostly-zeros
as is currently done? That would work just as well for gzip, and would
not sacrifice the ability to do 100x better than gzip.
-Chap
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: chap@anastigmatix.net, michael.paquier@gmail.com, amit.kapila16@gmail.com
Subject: Re: AdvanceXLInsertBuffer vs. WAL segment compressibility
In-Reply-To: <5796D9EB.6070407@anastigmatix.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox