Re: Compress ReorderBuffer spill files using LZ4 - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Compress ReorderBuffer spill files using LZ4
Date
Msg-id CAFiTN-ss5WpXboO5t7FXwsg9FwT_xoFH96Vds4723aiz-n3ohQ@mail.gmail.com
Whole thread Raw
In response to Re: Compress ReorderBuffer spill files using LZ4  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Fri, Jun 7, 2024 at 2:39 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2024-Jun-07, Dilip Kumar wrote:
>
> > I think the compression option should be supported at the CREATE
> > SUBSCRIPTION level instead of being controlled by a GUC. This way, we
> > can decide on compression for each subscription individually rather
> > than applying it to all subscribers. It makes more sense for the
> > subscriber to control this, especially when we are planning to
> > compress the data sent downstream.
>
> True.  (I think we have some options that are in GUCs for the general
> behavior and can be overridden by per-subscription options for specific
> tailoring; would that make sense here?  I think it does, considering
> that what we mostly want is to save disk space in the publisher when
> spilling to disk.)

Yeah, that makes sense.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Xiaoran Wang
Date:
Subject: XACT_EVENT for 'commit prepared'
Next
From: Dilip Kumar
Date:
Subject: Re: use CREATE DATABASE STRATEGY = FILE_COPY in pg_upgrade