Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iyTxi-0004ZS-Is for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Feb 2020 05:07:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iyTxf-0002Wr-31 for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Feb 2020 05:07:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iyTxe-0002T2-QJ for pgsql-hackers@lists.postgresql.org; Mon, 03 Feb 2020 05:07:50 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iyTxW-0003Zg-4Y for pgsql-hackers@postgresql.org; Mon, 03 Feb 2020 05:07:49 +0000 Received: from hnk.local (p1752128-ipbf1308funabasi.chiba.ocn.ne.jp [123.218.229.128]) by oss.nttdata.com (Postfix) with ESMTPSA id EC113606F7; Mon, 3 Feb 2020 14:07:35 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.101.5 at oss.nttdata.com Subject: Re: table partitioning and access privileges To: Amit Langote Cc: Tom Lane , Fujii Masao , PostgreSQL-development References: <6218.1577388354@sss.pgh.pa.us> <3546b691-b744-12c9-fd2f-7dc31c3c030e@oss.nttdata.com> <21015.1580400165@sss.pgh.pa.us> From: Fujii Masao Message-ID: <79ee190f-8219-6091-d2e5-ffae1bcf8d6e@oss.nttdata.com> Date: Mon, 3 Feb 2020 14:07:35 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------C6E1B90C89897C9FD9388D68" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------C6E1B90C89897C9FD9388D68 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 2020/02/03 11:05, Amit Langote wrote: > On Fri, Jan 31, 2020 at 9:39 PM Fujii Masao wrote: >> On 2020/01/31 13:38, Amit Langote wrote: >>> On Fri, Jan 31, 2020 at 1:28 AM Fujii Masao wrote: >>>> Fair enough. I finally did back-patch because the behavior is clearly >>>> documented and I failed to hear the opinions to object the back-patch. >>>> But I should have heard and discussed such risks more. >>>> >>>> I'm OK to revert all those back-patch. Instead, probably the document >>>> should be updated in old branches. >>> >>> I could find only this paragraph in the section on inheritance that >>> talks about how access permissions work: >>> >>> 9.4: >>> >>> "Note how table access permissions are handled. Querying a parent >>> table can automatically access data in child tables without further >>> access privilege checking. This preserves the appearance that the data >>> is (also) in the parent table. Accessing the child tables directly is, >>> however, not automatically allowed and would require further >>> privileges to be granted." >>> >>> 9.5-12: >>> >>> "Inherited queries perform access permission checks on the parent >>> table only. Thus, for example, granting UPDATE permission on the >>> cities table implies permission to update rows in the capitals table >>> as well, when they are accessed through cities. This preserves the >>> appearance that the data is (also) in the parent table. But the >>> capitals table could not be updated directly without an additional >>> grant. In a similar way, the parent table's row security policies (see >>> Section 5.7) are applied to rows coming from child tables during an >>> inherited query. A child table's policies, if any, are applied only >>> when it is the table explicitly named in the query; and in that case, >>> any policies attached to its parent(s) are ignored." >>> >>> Do you mean that the TRUNCATE exception should be noted here? >> >> Yes, that's what I was thinking. > > Okay. How about the attached? Thanks for the patches! You added the note just after the description about row level security on inherited table, but isn't it better to add it before that? Attached patch does that. Thought? > Maybe, we should also note the LOCK TABLE exception? Yes. Regards, -- Fujii Masao NTT DATA CORPORATION Advanced Platform Technology Group Research and Development Headquarters --------------C6E1B90C89897C9FD9388D68 Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0"; name="doc-inh-trunc-perms-95-12_fujii.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="doc-inh-trunc-perms-95-12_fujii.patch" ZGlmZiAtLWdpdCBhL2RvYy9zcmMvc2dtbC9kZGwuc2dtbCBiL2RvYy9zcmMvc2dtbC9kZGwu c2dtbAppbmRleCBkODg2NTFkZjllLi43NTUwZDAzZjI3IDEwMDY0NAotLS0gYS9kb2Mvc3Jj L3NnbWwvZGRsLnNnbWwKKysrIGIvZG9jL3NyYy9zZ21sL2RkbC5zZ21sCkBAIC0zMzg0LDcg KzMzODQsMTUgQEAgVkFMVUVTICgnQWxiYW55JywgTlVMTCwgTlVMTCwgJ05ZJyk7CiAgICBh Y2Nlc3NlZCB0aHJvdWdoIDxzdHJ1Y3RuYW1lPmNpdGllczwvc3RydWN0bmFtZT4uICBUaGlz IHByZXNlcnZlcyB0aGUgYXBwZWFyYW5jZQogICAgdGhhdCB0aGUgZGF0YSBpcyAoYWxzbykg aW4gdGhlIHBhcmVudCB0YWJsZS4gIEJ1dAogICAgdGhlIDxzdHJ1Y3RuYW1lPmNhcGl0YWxz PC9zdHJ1Y3RuYW1lPiB0YWJsZSBjb3VsZCBub3QgYmUgdXBkYXRlZCBkaXJlY3RseQotICAg d2l0aG91dCBhbiBhZGRpdGlvbmFsIGdyYW50LiAgSW4gYSBzaW1pbGFyIHdheSwgdGhlIHBh cmVudCB0YWJsZSdzIHJvdworICAgd2l0aG91dCBhbiBhZGRpdGlvbmFsIGdyYW50LiAgVHdv IGV4Y2VwdGlvbnMgdG8gdGhpcyBydWxlIGFyZQorICAgPGNvbW1hbmQ+VFJVTkNBVEU8L2Nv bW1hbmQ+IGFuZCA8Y29tbWFuZD5MT0NLIFRBQkxFPC9jb21tYW5kPiwKKyAgIHdoZXJlIHBl cm1pc3Npb25zIG9uIHRoZSBjaGlsZCB0YWJsZXMgYXJlIGFsd2F5cyBjaGVja2VkLAorICAg d2hldGhlciB0aGV5IGFyZSBwcm9jZXNzZWQgZGlyZWN0bHkgb3IgcmVjdXJzaXZlbHkgdmlh IHRob3NlIGNvbW1hbmRzCisgICBwZXJmb3JtZWQgb24gdGhlIHBhcmVudCB0YWJsZS4KKyAg PC9wYXJhPgorCisgIDxwYXJhPgorICAgSW4gYSBzaW1pbGFyIHdheSwgdGhlIHBhcmVudCB0 YWJsZSdzIHJvdwogICAgc2VjdXJpdHkgcG9saWNpZXMgKHNlZSA8eHJlZiBsaW5rZW5kPSJk ZGwtcm93c2VjdXJpdHkiLz4pIGFyZSBhcHBsaWVkIHRvCiAgICByb3dzIGNvbWluZyBmcm9t IGNoaWxkIHRhYmxlcyBkdXJpbmcgYW4gaW5oZXJpdGVkIHF1ZXJ5LiAgQSBjaGlsZCB0YWJs ZSdzCiAgICBwb2xpY2llcywgaWYgYW55LCBhcmUgYXBwbGllZCBvbmx5IHdoZW4gaXQgaXMg dGhlIHRhYmxlIGV4cGxpY2l0bHkgbmFtZWQK --------------C6E1B90C89897C9FD9388D68--