pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Robert Haas <robertmhaas@gmail.com>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Row-Level Security
Date: Mon, 14 Dec 2009 22:32:20 -0500
Message-ID: <603c8f070912141932k3ed0621cqc1051dfbf92a329f@mail.gmail.com> (raw)
In-Reply-To: <4B26E910.4060604@ak.jp.nec.com>
References: <20091212203003.GL17756@tamriel.snowman.net>
	<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>
	<603c8f070912140318i6bbc1d63o9e81d409d0b342b6@mail.gmail.com>
	<4B2626ED.7030104@kaigai.gr.jp>
	<20091214134714.GS17756@tamriel.snowman.net>
	<4B26E910.4060604@ak.jp.nec.com>

2009/12/14 KaiGai Kohei <kaigai@ak.jp.nec.com>:
> IIRC, one headache issue is that user may provide well indexable conditions,
> such as "SELECT * FROM view_x WHERE id = 1234". In this case, if we strictly
> keep the order of evaluation between inside and outside of the view, its
> performance penalty will over reasonable tradeoff to the better security.

If you don't allow the indexable qual to be pushed down into the view
in this situation, performance will be wretched.  I think we need to
distinguish between trusted and untrusted operations.  Everything in
the view definition is trusted.  And some other things... perhaps
access methods and some/most/all system catalog functions... are
trusted.  Other stuff is untrusted, and can't be pushed down.

I think there was a previous discussion of this when Heikki first
posted the issue to -hackers.

...Robert



view thread (165+ messages)  latest in thread

Message-ID: <603c8f070912141932k3ed0621cqc1051dfbf92a329f@mail.gmail.com>
Permalink:  ../603c8f070912141932k3ed0621cqc1051dfbf92a329f@mail.gmail.com/
Also on:    postgresql.org/message-id/603c8f070912141932k3ed0621cqc1051dfbf92a329f@mail.gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: robertmhaas@gmail.com, kaigai@ak.jp.nec.com, sfrost@snowman.net, kaigai@kaigai.gr.jp, josh@agliodbs.com
  Subject: Re: Row-Level Security
  In-Reply-To: <603c8f070912141932k3ed0621cqc1051dfbf92a329f@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox