Re: running logical replication as the subscription owner

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Jeff Davis <pgsql@j-davis.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Noah Misch <noah@leadboat.com>

Date: 2023-04-03T11:54:29Z

Lists: pgsql-hackers

On Thu, Mar 30, 2023 at 7:12 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> I don't think run_as_owner is terrible, despite the ambiguity. It's
> talking about the owner of the object on which the property is being
> set.
>

I find this justification quite reasonable to keep the option name as
run_as_owner. So, +1 to use the new option name as run_as_owner.

-- 
With Regards,
Amit Kapila.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Honor run_as_owner option in tablesync worker.
- a83edeaf684a 16.0 landed
Document new pg_subscription columns.
- bc25d6c54a00 16.0 landed
Add a run_as_owner option to subscriptions.
- 482675987bcd 16.0 landed
Perform logical replication actions as the table owner.
- 1e10d49b65d6 16.0 landed
Add new predefined role pg_create_subscription.
- c3afe8cf5a1e 16.0 cited
Respect permissions within logical replication.
- a2ab9c06ea15 15.0 cited
Empty search_path in logical replication apply worker and walsender.
- 11da97024abb 14.0 cited
Empty search_path in Autovacuum and non-psql/pgbench clients.
- 582edc369cdb 11.0 cited