Re: [PoC] Improve dead tuple storage for lazy vacuum - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: [PoC] Improve dead tuple storage for lazy vacuum
Date
Msg-id CAD21AoAYSw=mOyBKtCcQ+5vnk_KhzFEK3pq+yOkRJpqV0y1HwA@mail.gmail.com
Whole thread Raw
In response to Re: [PoC] Improve dead tuple storage for lazy vacuum  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers
On Tue, Mar 21, 2023 at 2:41 PM John Naylor
<john.naylor@enterprisedb.com> wrote:
>
>
> On Mon, Mar 20, 2023 at 9:34 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> > On Mon, Mar 20, 2023 at 9:34 PM John Naylor
> > <john.naylor@enterprisedb.com> wrote:
> > > That's an interesting idea, and the analogous behavior to aset could be a good thing for readability and
maintainability.Worth seeing if it's workable. 
> >
> > I've attached a quick hack patch. It can be applied on top of v32
> > patches. The changes to dsa.c are straightforward since it makes the
> > initial and max block sizes configurable.
>
> Good to hear -- this should probably be proposed in a separate thread for wider visibility.

Agreed. I'll start a new thread for that.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Data is copied twice when specifying both child and parent table in publication
Next
From: Kurlaev Jaroslav
Date:
Subject: RE: Smoothing the subtrans performance catastrophe