Horton

Re: Add pg_get_acl() function get the ACL for a database object

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Joel Jacobson <joel@compiler.org>, Isaac Morland <isaac.morland@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-06-21T03:44:48Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add pg_get_acl() to get the ACL for a database object

  2. doc: Add ACL acronym for "Access Control List"

Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Jun 20, 2024 at 08:32:57AM +0200, Joel Jacobson wrote:
>> I've added overloaded versions for regclass and regproc so far:
>> 
>> \df pg_get_acl
>> List of functions
>> Schema   |    Name    | Result data type |  Argument data types   | Type
>> ------------+------------+------------------+------------------------+------
>> pg_catalog | pg_get_acl | aclitem[]        | classid oid, objid oid | func
>> pg_catalog | pg_get_acl | aclitem[]        | objid regclass         | func
>> pg_catalog | pg_get_acl | aclitem[]        | objid regproc          | func
>> (3 rows)

> Interesting idea.

Doesn't that result in "cannot resolve ambiguous function call"
failures?

			regards, tom lane