RE: pg_createsubscriber does not check output_plugin_libraries - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: pg_createsubscriber does not check output_plugin_libraries
Date
Msg-id OS9PR01MB12149FF45141BEBC1053048FCF5BE2@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread
In response to Re: pg_createsubscriber does not check output_plugin_libraries  (Jacob Champion <jacob.champion@enterprisedb.com>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add PRODUCT() aggregate function
Next
From: "chee.wooson"
Date:
Subject: Re: Recovery conflict resolution misses backends that import snapshots