| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Subject: | Re: about truncate |
| Date: | 2009-01-09 13:58:54 |
| Message-ID: | 19628.1231509534@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>> This area is under SQL standard control, so we can't really invent our
>>> own behavior.
>> What *would* do the right thing here, or would anything?
> I think we don't need GRANT to be recursive, but instead the permission
> checks at runtime should allow
> SELECT * FROM persons;
> to succeed even if there are no permissions on "employees".
Hmm, if we are supposing that the spec should control this, then
surely we can find chapter and verse spelling out what should happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-09 14:12:15 | foreign_data test fails with non-C locale |
| Previous Message | Peter Eisentraut | 2009-01-09 13:48:47 | Re: about truncate |