| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "akapila(at)postgresql(dot)org" <akapila(at)postgresql(dot)org>, "nisha(dot)moond412(at)gmail(dot)com" <nisha(dot)moond412(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: REASSIGN OWNED vs. relisshared dep on !relisshared |
| Date: | 2026-07-19 06:34:00 |
| Message-ID: | OS9PR01MB12149850735EFCD9B9CF444FCF5C42@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Hackers,
> > OK, should we go ahead and split the pg_subscription catalog for v20
> > then? Maybe pg_subscription (shared) and pg_subscription_db (per-
> > database)?
> >
>
> +1, though I am not sure of catalog names. We can brainstorm those
> during development.
+1. I cannot come up with better idea to resolve the entanglement. I briefly
checked the launcher code and it read 7 attributes [1] at least. Not verified,
all of them (or except name) can be retained on the shared catalog.
If it's ok I can start a separated thread after analyzing bit more with the PoC.
[1]:
```
oid
dbid
name
owner
retaindeadtuples
retentionactive
enabled
```
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-07-19 08:05:41 | Re: Checkpointer write combining |
| Previous Message | Tatsuo Ishii | 2026-07-19 06:32:27 | Re: Row pattern recognition |