Re: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?
Дата
Msg-id CAKFQuwa_KjSwVoDfsRLVb320aMVkx3CynsW8dwxLoyrVWNGW7Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?  (Zhaoxun Yan <yan.zhaoxun@gmail.com>)
Список pgsql-admin
On Thursday, October 12, 2023, Zhaoxun Yan <yan.zhaoxun@gmail.com> wrote:

Now pg_rewind has no problem when user=rewinder & dbname=repmgr:
$ pg_rewind -D /pgdata --source-server='host=172.17.1.2 port=5432 user=rewinder dbname=repmgr   connect_timeout=5'
pg_rewind: source and target cluster are on the same timeline
pg_rewind: no rewind required

Still, I wish psql can specify this database limitation explicitly, either enforcing the command with 'IN DATABASE [dbname]', or emphasize it in feedback rather than a simple 'GRANT'.

Please no. All objects only exist in a single database and you must be signed into a database to execute SQL, and you cannot execute cross-database. Specifying “in database” would just be annoying and redundant.  Same goes with a message saying “you executed this command in database postgres.”  Especially for grant, where the worst that happens is you still can’t do something you thought you enabled.

David J.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Zhaoxun Yan
Дата:
Сообщение: Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?
Следующее
От: Rajesh Kumar
Дата:
Сообщение: Re: Automation