Request a Demo
Home   >   mailing lists

Re: Adding REPACK [concurrently] - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Adding REPACK [concurrently]
Date
Msg-id CAA4eK1LFqdh4=b4t3OTpmCMs211-9dJEG8JdcV1ikN94LBum9w@mail.gmail.com
Whole thread
Responses RE: Adding REPACK [concurrently]
List pgsql-hackers
Tree view 
On Wed, May 27, 2026 at 5:31 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, May 27, 2026 at 1:08 AM Zhijie Hou (Fujitsu)
> <houzj.fnst@fujitsu.com> wrote:
> >
> > 0001 remains unchanged.
> >
>
> Few minor comments:
> =================

Commit message says: "This change does not advance catalog_xmin.
REPACK already holds a snapshot that prevents catalog dead tuple
removal, so catalog_xmin handling can be addressed independently.".
Isn't it equally important to advance this, otherwise, for long
running REPACKs dead tuples will be accumulated needlessly? If so, do
we have any ideas to avoid this?

--
With Regards,
Amit Kapila.

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Adding REPACK [concurrently]