On Tue, 2020-02-18 at 15:06 -0500, Stephen Frost wrote:
>
> Policies, also being part of the overall privilege system, could
> certainly be looked at in a similar light as being different from
> triggers and indexes...
While I think I agree with Stephen here, I don't have a vested interest
in an
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Marc Munro writes:
> > On Mon, 2020-02-17 at 22:48 -0500, Tom Lane wrote:
> >> An RLS policy is a table "subsidiary object" so it only depends indirectly
> >> on the extension that owns the table.
>
> > Yep, I get that, and I see the dependency
On Mon, 2020-02-17 at 22:48 -0500, Tom Lane wrote:
> Marc Munro writes:
> >
> An RLS policy is a table "subsidiary object" so it only depends
> indirectly
> on the extension that owns the table.
Yep, I get that, and I see the dependency chain in the catalog.
However an extension can create the
Marc Munro writes:
> On Mon, 2020-02-17 at 22:48 -0500, Tom Lane wrote:
>> An RLS policy is a table "subsidiary object" so it only depends indirectly
>> on the extension that owns the table.
> Yep, I get that, and I see the dependency chain in the catalog.
> However an extension can create the
Marc Munro writes:
> I tried to define a policy within an extension but the policy does not
> seem to belong to the extension. Is this the way it is supposed to be?
Yeah, I would expect that.
https://www.postgresql.org/docs/current/extend-extensions.html
says:
The kinds of SQL objects tha
On 2/17/20 2:46 PM, Marc Munro wrote:
I tried to define a policy within an extension but the policy does not
seem to belong to the extension. Is this the way it is supposed to be?
This is postgres 9.5.21
Here is the relevant code from the extension:
create table rls2 (
username te
