From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] replace GrantObjectType with ObjectType |
Date: | 2017-12-20 15:23:53 |
Message-ID: | d1423a49-dc53-5f88-9a6b-7e067dd8995e@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/19/17 19:56, Michael Paquier wrote:
> -stringify_adefprivs_objtype(GrantObjectType objtype)
> +stringify_adefprivs_objtype(ObjectType objtype)
> [...]
> + default:
> + elog(ERROR, "unrecognized grant object type: %d", (int) objtype);
> + return "???"; /* keep compiler quiet */
> }
> -
> - elog(ERROR, "unrecognized grant object type: %d", (int) objtype);
> - return "???"; /* keep compiler quiet */
> Still this portion in 0001 is something that we try to avoid as much
> as possible, no? I would have thought that all object types should be
> listed directly so as nothing is missed in the future.
But we don't really know what such future GRANT commands would actually
look like. What would the GRANT syntax corresponding to OBJECT_CAST or
OBJECT_STATISTIC_EXT be? I think that's best filled in when we know.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-12-20 15:29:14 | Re: AS OF queries |
Previous Message | Peter Eisentraut | 2017-12-20 15:20:08 | Re: [HACKERS] static assertions in C++ |