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

From Antonin Houska
Subject Re: Adding REPACK [concurrently]
Date
Msg-id 26358.1767625172@localhost
Whole thread Raw
In response to Re: Adding REPACK [concurrently]  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> On 2026-Jan-05, Antonin Houska wrote:
>
> > Mihail Nikalayeu <mihailnikalayeu@gmail.com> wrote:
>
> > > Probably it is because
> > > > 100000L,    /* XXX Tune the delay. */
> > >
> > > 100 seconds is clearly too much.
> >
> > I confused milliseconds with microseconds. Since I was only running the code
> > with debugger, the long delays didn't appear to be a problem.
> >
> > Instead of tuning the timeout, I'm thinking of introducing a condition
> > variable that signals WAL flushing.
>
> I think there is a patch that adds support for this in the queue already
> -- see this message:
> https://postgr.es/m/CAPpHfds-KiZRuCruc0jHxLSxLqzKcHJGwOFFA0b_RgaJvtUOEQ@mail.gmail.com

Thanks for the hint! It seems that the already committed WaitForLSN() function
does what I need.

--
Antonin Houska
Web: https://www.cybertec-postgresql.com



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Precompute string lengths in PerformRadiusTransaction
Next
From: vignesh C
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication