| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Markus Wanner <markus(at)bluegap(dot)ch>, Alex Hunsaker <badalex(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New patch for Column-level privileges |
| Date: | 2009-01-13 17:33:30 |
| Message-ID: | 28398.1231868010@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Oh, I didn't see that. Still, this doesn't test whether the behavior
>> is correct with respect to ADD/DROP COLUMN --- if that were implemented
>> like SELECT * you'd not see any change in the regression result.
> Hrm. If a column is added and you're not granted SELECT rights on it
> (even if you have access to all the originals), it should start failing
> for you. I can certainly add a test case to cover that though. Or is
> that not the behavior you're expecting?
Right, and conversely dropping the last non-granted column should make
it work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-01-13 18:06:44 | Re: [BUGS] Status of issue 4593 |
| Previous Message | Simon Riggs | 2009-01-13 17:31:55 | Re: Latest version of Hot Standby patch |