Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5rg-0008MQ-Tf for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Aug 2013 17:18:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VF5rg-0007O2-Dw for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Aug 2013 17:18:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5rf-0007Nu-8m for pgsql-hackers@postgresql.org; Thu, 29 Aug 2013 17:18:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5rc-0000FU-JI for pgsql-hackers@postgresql.org; Thu, 29 Aug 2013 17:18:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id r7THILxu009408; Thu, 29 Aug 2013 13:18:21 -0400 From: Tom Lane To: Josh Berkus cc: Kohei KaiGai , "ktm@rice.edu" , Alexander Korotkov , Oleg Bartunov , Greg Smith , PgHacker Subject: Re: [v9.4] row level security In-reply-to: <521F7DFB.8060602@agliodbs.com> References: <51E8A8C1.2050700@2ndQuadrant.com> <20130719030347.GV15510@tamriel.snowman.net> <51E8ADD9.5020600@2ndQuadrant.com> <521D1C2B.8090503@2ndQuadrant.com> <20130829142321.GA30496@aart.rice.edu> <521F7DFB.8060602@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Thu, 29 Aug 2013 09:59:39 -0700" Date: Thu, 29 Aug 2013 13:18:21 -0400 Message-ID: <9407.1377796701@sss.pgh.pa.us> X-Pg-Spam-Score: -4.4 (----) 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 Josh Berkus writes: > It's one thing to day "we can't solve this covert channel issue right > now in this patch", but saying "we don't plan to solve it at all" is > likely to doom the patch. > I'm not sure what the solution would be, exactly. Deny permission for > EXPLAIN on certain tables? That would close only one covert channel. Others were already pointed out upthread, and I'll bet there are more ... regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers