| From: | Evgeniy Efimkin <efimkin(at)yandex-team(dot)ru> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Дмитрий Сарафанников <dsarafan(at)yandex-team(dot)ru>, Андрей Бородин <x4mmm(at)yandex-team(dot)ru>, Владимир Бородин <root(at)simply(dot)name> |
| Subject: | Re: Special role for subscriptions |
| Date: | 2018-11-08 08:11:37 |
| Message-ID: | 2244061541664697@iva5-815ce03d682b.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
I think we can add FOR TABLES clause for create/refresh subscription, for example: CREATE SUBSCRIPTION my_sub CONNECTION ... PUBLICATION my_pub [WITH ...] [ FOR TABLES t1, t2 | ALL TABLES ]. ALL TABLES is avalibale only for superuser. FOR TABLES t1, t2 is available to owner of tables and superuser.
07.11.2018, 00:52, "Stephen Frost" <sfrost(at)snowman(dot)net>:
> Greetings,
>
> * Evgeniy Efimkin (efimkin(at)yandex-team(dot)ru) wrote:
>> As a first step I suggest we allow CREATE SUBSCRIPTION for table owner only.
>
> That's a nice idea but seems like we would want to have a way to filter
> what tables a subscription follows then..? Just failing if the
> publication publishes tables that we don't have access to or are not the
> owner of seems like a poor solution..
>
> Thanks!
>
> Stephen
--------
Ефимкин Евгений
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2018-11-08 08:21:59 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Previous Message | Konstantin Knizhnik | 2018-11-08 08:08:25 | Re: [HACKERS] Surjective functional indexes |