Re: [HACKERS] SUBSCRIPTIONS and pg_upgrade - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [HACKERS] SUBSCRIPTIONS and pg_upgrade
Date
Msg-id 20170217222141.GX9812@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] SUBSCRIPTIONS and pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] SUBSCRIPTIONS and pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Peter,

* Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
> On 2/17/17 09:33, Stephen Frost wrote:
> >> One reason is that pg_subscription is only readable by a superuser, so
> >> we can't even dump them unless we're superuser.
> > Sure, but that's true of roles and other things..  On a system with RLS,
> > likely only the database superuser can actually read everything.
>
> There are some concurrent discussions about getting a list of
> subscriptions without having superuser.  Once that is resolved, we'll
> likely have more options here, such as dumping only subscriptions you
> are owner of or something like that.

I certainly agree that we should provide a way to view subscriptions,
and perhaps do other things with them, without being a superuser.

I was going to suggest that it might make sense to have a role attribute
or a default role created for managing publications/subscriptions.  It
seems like this should be independent of the existing replicaiton role
attribute, which is about physical replication.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] SUBSCRIPTIONS and pg_upgrade
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting forcheckpoint