From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Privileges and inheritance |
Date: | 2009-10-05 08:22:17 |
Message-ID: | 1254730937.25576.8.camel@fsopti579.F-Secure.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2009-10-05 at 16:27 +0900, KaiGai Kohei wrote:
> CREATE TABLE tbl_p (int a, int b);
> CREATE TABLE tbl_c (int x) INHERITS(tbl_p);
>
> SELECT a,b FROM tbl_p; --> It selects data from only tbl_p.
> It is reasonable to bypass checks on tbl_c.
> SELECT b,x FROM tbl_c; --> It selects data from tbl_p and tbl_c concurrently,
> if we consider the inherited columns are a part of
> the parent table.
I think you need to distinguish between the definition of columns and
the data in the columns. tbl_c has inherited the definition of the
columns from tbl_p, but the data is part of tbl_c, not tbl_p. So there
is not reason for this second query to ask tbl_p for permission, because
it does not touch data in tbl_p at all.
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2009-10-05 08:39:59 | Re: Rules: A Modest Proposal |
Previous Message | Simon Riggs | 2009-10-05 08:22:16 | Re: Privileges and inheritance |