Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock
Date: 2026-10-07 00:50:16
Message-ID: CAGRkXqQMfEUgG_TtkZDRs6fSFsSbGoYHBXnd8+XHvarNGcodvA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> > [ I assume this is not meant for v19, is it? ]

> I definitely dont't want to change this behavior in 19. At the most,
> lets document any shortcomings that the current behavior may have.

Right, this is for 20, not 19. I will leave 19 alone and come back to
it once 19 is out. .

Antonin, thanks for your proposal. I will review your patch little later.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-10-07 00:50:29 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Previous Message Peter Geoghegan 2026-10-07 00:43:59 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops