Re: BUG #15833: defining a comment on a domain constraint fails with wrong OID
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: clemens@ladisch.de, pgsql-bugs@lists.postgresql.org
Date: 2019-06-07T05:42:33Z
Lists: pgsql-bugs
On Wed, Jun 05, 2019 at 02:15:02PM -0400, Alvaro Herrera wrote: > Confirmed. It works for superusers, which explains why the existing > regression tests pass -- and that's because check_object_ownership() > (which is handing the OBJECT_DOMCONSTRAINT case wrongly) is bypassed for > superusers. Annoyingly, get_object_address does not return the type's > OID, only the domain's. Well, it wouldn't be a problem to do a syscache lookup and then use the type from contypid, no? It seems to me that it would be more consistent to just add a pg_domain_constraint_ownercheck() in aclchk.c as all the syscache lookups happen their for all the other objects types. What do you think? -- Michael
Commits
-
Fix handling of COMMENT for domain constraints
- 13f4b462dbe8 9.5.18 landed
- ff1a25601e75 9.6.14 landed
- 56a932533aa2 10.9 landed
- fa5f3a4bcca7 11.4 landed
- ceac4505d342 12.0 landed