Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TfXti-0005dV-AA for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Dec 2012 15:25:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TfXth-0004fL-Py for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Dec 2012 15:25:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TfXtf-0004e6-W4 for pgsql-hackers@postgresql.org; Mon, 03 Dec 2012 15:25:28 +0000 Received: from 173-164-140-181-sfba.hfc.comcastbusiness.net ([173.164.140.181] helo=fetter.org) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TfXtb-0005sg-W8 for pgsql-hackers@postgresql.org; Mon, 03 Dec 2012 15:25:26 +0000 Received: by fetter.org (Postfix, from userid 500) id F319F301975; Mon, 3 Dec 2012 07:25:21 -0800 (PST) Date: Mon, 3 Dec 2012 07:25:21 -0800 From: David Fetter To: Kohei KaiGai Cc: Robert Haas , Alvaro Herrera , Dean Rasheed , Tom Lane , Florian Pflug , PgHacker Subject: Re: [v9.3] Row-Level Security Message-ID: <20121203152521.GA16951@fetter.org> References: <20121018181956.GL3763@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Sun, Nov 25, 2012 at 03:20:28PM +0100, Kohei KaiGai wrote: > > However, UPDATE / DELETE support is not perfect right now. > > In case when we try to update / delete a table with inherited > > children and RETURNING clause was added, is loses right > > references to the pseudo columns, even though it works fine > > without inherited children. > > > The attached patch fixed this known problem. This patch no longer applies to git master. Any chance of a rebase? Also, might this approach work for the catalog? The use case I have in mind is multi-tenancy, although one can imagine organizations where internal access controls might be required on it, too. Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers