From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |
Date: | 2016-07-27 00:20:32 |
Message-ID: | 5797FE50.7070600@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/26/16 20:01, Michael Paquier wrote:
> On Tue, Jul 26, 2016 at 9:48 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> Does any body else see the use case
>> reported by Chapman important enough that we try to have some solution
>> for it in-core?
>
> The lack of updates in the pg_lesslog project is a sign that it is not
> that much used. I does not seem a good idea to bring in-core a tool
> not used that much by users.
Effectively, it already was brought in-core in commit 9a20a9b.
Only, that change had an unintended consequence that *limits*
compressibility - and it would not have that consequence, if
it were changed to simply set xlp_pageaddr to InvalidXLogRecPtr
in the dummy zero pages written to fill out a segment.
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2016-07-27 00:22:01 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |
Previous Message | Michael Paquier | 2016-07-27 00:01:57 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |