Greetings,
* Vik Fearing (v...@postgresfriends.org) wrote:
> So I have to manually do a diff of the two acls and generate
> GRANT/REVOKE statements? That's not encouraging. :(
Not sure if it's helpful to you, but pg_dump has code that generates SQL
to do more-or-less exactly this.
Thanks,
Step
Vik Fearing writes:
> Ok, so not safe. Should we remove makeaclitem() then?
Well, I wouldn't recommend poking values into an ACL with it,
but it seems like it has potential use in queries too, say
select * from pg_class
where makeaclitem('joe'::regrole, 'bob'::regrole, 'select', false) =
any(r
On 03/03/2020 19:02, Tom Lane wrote:
> Vik Fearing writes:
>> I have a few questions about setting acl on SQL level.
>> Is it safe to do something like
>> UPDATE pg_class SET relacl = $1 WHERE oid = $2;
>> ?
>
>> I don't think it is because Exe
Vik Fearing writes:
> I have a few questions about setting acl on SQL level.
> Is it safe to do something like
> UPDATE pg_class SET relacl = $1 WHERE oid = $2;
> ?
> I don't think it is because ExecGrant_* call updateAclDependencies after
> they do the update and my
I have a few questions about setting acl on SQL level.
Is it safe to do something like
UPDATE pg_class SET relacl = $1 WHERE oid = $2;
?
I don't think it is because ExecGrant_* call updateAclDependencies after
they do the update and my own update would not do that. But is it safe
to
