From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: has_column_privilege behavior (was Re: Assert failed in snprintf.c) |
Date: | 2018-10-01 21:11:41 |
Message-ID: | 20181001211140.GJ4184@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > My complaint is specifically trying to do something like:
[...]
> That code is kinda broken anyway, because it won't survive relation drops
> either. What you *should* be writing is
Yes, I agree, but it still seems like we're throwing an ERROR
unnecessairly.
> Having said that, I'm fine with having it return NULL if the given
> attname matches an attisdropped column.
Ok, that's really all I was asking about.
> ... What I was on about is what
> happens when you write
>
> has_column_privilege('sometab'::regclass, 'somecol', 'SELECT');
>
> and sometab exists but somecol doesn't.
Yeah, having that throw an error seems reasonable to me.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Larry Rosenman | 2018-10-01 21:15:01 | Re: Odd 9.4, 9.3 buildfarm failure on s390x |
Previous Message | Tom Lane | 2018-10-01 21:11:02 | Re: Odd 9.4, 9.3 buildfarm failure on s390x |