| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Antonin Houska <ah(at)cybertec(dot)at> |
| Subject: | Re: Adding REPACK [concurrently] |
| Date: | 2025-08-28 21:39:49 |
| Message-ID: | 202508282139.j24af7vwn7pz@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Aug-21, Mihail Nikalayeu wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>:
> > I proposed to leave this part out initially, which is why it hasn't been
> > reposted. We can review and discuss after the initial patches are in.
>
> I think it is worth pushing it at least in the same release cycle.
If others are motivated enough to certify it, maybe we can consider it.
But I don't think I'm going to have time to get this part reviewed and
committed in time for 19, so you might need another committer.
> > Because having an MVCC-safe mode has drawbacks, IMO we should make it
> > optional.
>
> Do you mean some option for the command? Like REPACK (CONCURRENTLY, SAFE)?
Yes, exactly that.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La grandeza es una experiencia transitoria. Nunca es consistente.
Depende en gran parte de la imaginación humana creadora de mitos"
(Irulan)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-28 21:46:39 | Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt |
| Previous Message | Nathan Bossart | 2025-08-28 21:35:25 | make LWLockCounter a global variable |