| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:23:41 |
| Message-ID: | 20090113172341.GD4656@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> What I see being tested is SELECT *, which is a different animal
> >> entirely.
>
> > Wouldn't this test cover those?
> > SELECT atest5 FROM atest5; -- fail
>
> 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?
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-01-13 17:29:02 | Re: [BUGS] Status of issue 4593 |
| Previous Message | Tom Lane | 2009-01-13 17:16:28 | Re: [BUGS] Status of issue 4593 |