Re: [HACKERS] Provide list of subscriptions and publications inpsql's completion - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Provide list of subscriptions and publications inpsql's completion
Date
Msg-id CAB7nPqS9eLJch3q=_OttVKgapPrcw1fcoMSbYaKRYEy0SjVwdQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Provide list of subscriptions and publications inpsql's completion  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: [HACKERS] Provide list of subscriptions and publications inpsql's completion
Re: [HACKERS] Provide list of subscriptions and publications inpsql's completion
List pgsql-hackers
On Sun, Feb 5, 2017 at 5:04 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> With this patch, when normal users type TAB after SUBSCRIPTION,
> they got "permission denied" error. I don't think that's acceptable.

Right, I can see that now. pg_stat_get_subscription() does not offer
as well a way to filter by databases... Perhaps we could add it? it is
stored as LogicalRepWorker->dbid so making it visible is sort of easy.

> In "CREATE SUBSCRIPTION ... PUBLICATION" and "ALTER SUBSCRIPTION ... SET
> PUBLICATION" cases, the publication defined in the publisher side should be
> specified. But, with this patch, the tab-completion for PUBLICATION shows
> the publications defined in local server (ie, subscriber side in those cases).
> This might be confusing.

Which would mean that psql tab completion should try to connect the
remote server using the connection string defined with the
subscription to get this information, which looks unsafe to me. To be
honest, I'd rather see a list of local objects defined than nothing..
-- 
Michael



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: [HACKERS] 0/NULL/NIL assignments in build_*_rel()
Next
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: pageinspect: Try to fix some bugs in previous commit.