| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net> |
| Subject: | Re: Adding REPACK [concurrently] |
| Date: | 2026-04-07 12:33:50 |
| Message-ID: | 202604071230.b5axxf3qna3m@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2026-Apr-07, Amit Kapila wrote:
> I have a question based on 0001's commit message: "This patch adds a
> new option to logical replication output plugin, to declare that it
> does not use shared catalogs (i.e. catalogs that can be changed by
> transactions running in other databases in the cluster).". In which
> cases, currently plugin needs to access multi-database transactions or
> transactions that need to access shared catalogs and on what basis a
> plugin can decide that the changes it requires won't need any such
> access.
I don't think any plugin needs "multi-database" access as such, but
needing access to shared catalogs is likely normal. Repack knows it
won't access any shared catalogs, so it can set the flag at ease.
There's a cross-check added in the commit that tests for access to
shared catalogs if the flag is set to false. I guess you could set it
to false and see what breaks :-)
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2026-04-07 12:36:01 | Re: EXPLAIN: showing ReadStream / prefetch stats |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-04-07 12:32:32 | RE: Adding REPACK [concurrently] |