Re: RLS policy dump/restore failure due to elided type-casts - Mailing list pgsql-general

From David G. Johnston
Subject Re: RLS policy dump/restore failure due to elided type-casts
Date
Msg-id CAKFQuwaiBXNFyFXAezOqyopYFgJ-cAn+Fe4MCt_y1eMgp9y3uQ@mail.gmail.com
Whole thread Raw
In response to RLS policy dump/restore failure due to elided type-casts  (Karl Czajkowski <karlcz@isi.edu>)
Responses Re: RLS policy dump/restore failure due to elided type-casts
List pgsql-general
On Wed, Apr 20, 2016 at 5:18 PM, Karl Czajkowski <karlcz@isi.edu> wrote:

  CREATE POLICY delete_stuff ON stuff
  FOR DELETE USING ('example attribute value' = ANY ( ((SELECT current_attributes()))::text[] ));


The following (untested) structure should be immune to this problem...use the knowledge as you see ​fit.

USING ('example_attribute_value' = ANY ( ARRAY( SELECT unnest(attr) FROM current_attributes() ca (attr) ) )

I cannot imagine the ARRAY(...) being removed and its presence should force the scalar = ANY(array) interpretation.

This does seem broken and likely to be back-patched though - and unnest+ARRAY is definitely inefficient so there is a trade-off involved - but hopefully only in the short-term (a couple of months probably...?).

David J.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: RLS policy dump/restore failure due to elided type-casts
Next
From: "David G. Johnston"
Date:
Subject: Re: RLS policy dump/restore failure due to elided type-casts