I had not seen this. > -----Original Message----- > From: pgsql-hackers-ow...@postgresql.org > [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Robert Haas > Sent: Montag, 28. September 2015 21:43 > To: Stephen Frost <sfr...@snowman.net> > Cc: Peter Eisentraut <pete...@gmx.net>; pgsql-hackers > <pgsql-hackers@postgresql.org>; Charles Clavadetscher > <clavadetsc...@swisspug.org> > Subject: Re: [HACKERS] unclear about row-level security USING vs. CHECK > > On Mon, Sep 28, 2015 at 3:15 PM, Stephen Frost <sfr...@snowman.net> wrote: > > I listed out the various alternatives but didn't end up getting any > > responses to it. I'm still of the opinion that the documentation is the > > main thing which needs improving here, but we can also change CREATE > > POLICY, et al, to require an explicit WITH CHECK clause for the commands > > where that makes sense if that's the consensus. > > My vote is to remove the behavior where USING flows over to WITH > CHECK. So you only get a WITH CHECK policy if you explicitly specify > one. > > If there's some other consensus, OK, but tempus fugit.
If the behaviof of USING doesn't flow to WITH CHECK is the same as making WITH CHECK mandatory for ALL and UPDATE, I guess. Otherwise there would be a partially unspecified behavior. Or am I misunderstanding your idea? Charles -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
