Re: Sorting out acl fixes

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sorting out acl fixes
Date: 2004-07-22 03:41:24
Message-ID: 40FF3764.7030809@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The solution I had in mind was for ALTER OWNER to run through the ACL
> and replace the old owner ID with the new one wherever the old one
> appears, in both grantor and grantee positions. So in your example
> {chriskl=arwdRxt/chriskl,other=r/chriskl}
> becomes
> {gumby=arwdRxt/gumby,other=r/gumby}
>
> You could skip doing this when the ACL is null of course, since the
> default assumption about its contents will change in just the same way.

What about fixing existing bad acls? I can't figure out a grant or
revoke statement to do it? Do I have to update to set the relacl to
null and then re-run the fixed set of grants?

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-22 03:42:22 Re: [HACKERS] Point in Time Recovery
Previous Message Bruce Momjian 2004-07-22 03:36:05 Re: [HACKERS] Point in Time Recovery