| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Jacob Champion' <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: pg_createsubscriber does not check output_plugin_libraries |
| Date: | 2026-09-11 02:51:01 |
| Message-ID: | OS9PR01MB12149FF45141BEBC1053048FCF5BE2@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As long as everyone is in agreement that --dry-run *should* be
> performing those checks in the first place, I'm happy.
Yes, it's my intention. Fujii-san, how do you feel? If you're OK, we can proceed.
> Even for PG17, specifying a non-superuser in the connection string
> leads to a successful --dry-run, then fails during normal operation.
To confirm, is it allowed to add such a verification in back branches?
I imagined running something like below after connecting to the publisher.
```
SELECT rolsuper
FROM pg_catalog.pg_roles
WHERE rolname = session_user;
```
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chee.wooson | 2026-09-11 02:51:30 | Re: Recovery conflict resolution misses backends that import snapshots |
| Previous Message | Tom Lane | 2026-09-11 02:46:00 | Re: Add PRODUCT() aggregate function |