| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Provide list of subscriptions and publications in psql's completion |
| Date: | 2017-02-17 14:37:25 |
| Message-ID: | 20170217143725.GN9812@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Peter Eisentraut (peter(dot)eisentraut(at)2ndquadrant(dot)com) wrote:
> On 2/13/17 12:07, Fujii Masao wrote:
> > Anyway IMO that we can expose all the
> > columns except the sensitive information (i.e., subconninfo field)
> > in pg_subscription to even non-superusers.
>
> You mean with column privileges?
>
> We could probably do that. I don't know if we have done that before on
> system catalogs.
I don't believe we have, though I'm not against doing so. I can't think
of any reason off-hand why it wouldn't work.
If we did that then perhaps we could remove some of the other views that
we have which are just to provide a subset of the columns of some other
table (eg: pg_roles)...
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2017-02-17 14:51:58 | Question about memory contexts in ReindexMultipleTables() |
| Previous Message | Stephen Frost | 2017-02-17 14:33:32 | Re: SUBSCRIPTIONS and pg_upgrade |