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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zhaoxun Yan <yan(dot)zhaoxun(at)gmail(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?
Date: 2023-10-13 02:03:58
Message-ID: 1430191.1697162638@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Zhaoxun Yan <yan(dot)zhaoxun(at)gmail(dot)com> writes:
> The results are the same, 'dbname=repmgr' is the root cause of the error,
> since 'dbname=postgres' went well with both 'user=rep' and 'user=rewinder',
> while 'dbname=repmgr' generates exactly the same error.

As far as I can tell, you granted permissions on that function
in the postgres database, but not any other database. Function
permissions, like most others, are database-local in Postgres.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2023-10-13 02:21:34 Re: Locks analyze
Previous Message Zhaoxun Yan 2023-10-13 01:41:48 Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'?