Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 68714632848 for ; Mon, 14 Dec 2009 04:59:17 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 25286-06 for ; Mon, 14 Dec 2009 08:59:10 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by mail.postgresql.org (Postfix) with ESMTP id EB2A5632486 for ; Mon, 14 Dec 2009 04:59:09 -0400 (AST) Received: from mailgate3.nec.co.jp ([10.7.69.161]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id nBE8wco5023584; Mon, 14 Dec 2009 17:58:38 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id nBE8wc218984; Mon, 14 Dec 2009 17:58:38 +0900 (JST) Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id nBE8wbrt021713; Mon, 14 Dec 2009 17:58:37 +0900 (JST) Received: from shoin.jp.nec.com ([10.26.220.3] [10.26.220.3]) by mail03.kamome.nec.co.jp with ESMTP id BT-MMP-27900; Mon, 14 Dec 2009 17:58:18 +0900 Received: from [10.19.71.82] ([10.19.71.82] [10.19.71.82]) by mail.jp.nec.com with ESMTP; Mon, 14 Dec 2009 17:58:18 +0900 Message-ID: <4B25FE28.40709@ak.jp.nec.com> Date: Mon, 14 Dec 2009 17:58:16 +0900 From: KaiGai Kohei User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Robert Haas CC: KaiGai Kohei , Josh Berkus , Stephen Frost , pgsql-hackers@postgresql.org Subject: Re: Row-Level Security References: <20091212203003.GL17756@tamriel.snowman.net> <4B24381F.7050407@agliodbs.com> <603c8f070912121918i59f807e3n5ed4d4699227e43@mail.gmail.com> <4B24AAED.2080706@kaigai.gr.jp> <603c8f070912130411q765c7e9aw371b468229b8e32@mail.gmail.com> <4B25C5B2.9010108@ak.jp.nec.com> <603c8f070912132135l43bdf060sa5207b5a4d2c918c@mail.gmail.com> <4B25DE99.2050801@ak.jp.nec.com> In-Reply-To: <4B25DE99.2050801@ak.jp.nec.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200912/1166 X-Sequence-Number: 151869 One more issue I found. What row-level policy should be applied on inherited tables? If inconsistent policy is applied on the parent and child table, we can see different result set, although a part of result set in the parent table come from the child table. My idea is to copy row-level policies to inherited tables from the parent table. We can additional row-level policy on the inherited tables, but all the condition is chained by AND, so here is no inconsistency. Even if the inherited table has multiple parents, all the row-level policies shall be applied, so here is no inconsistency. (Needless to say, child table have same columns, so we can apply same row-level policies.) Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei