From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Proposed TODO: CREATE .... WITH OWNER; |
Date: | 2004-10-24 16:39:40 |
Message-ID: | 200410240939.41443.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dennis,
> Another observation is that SET SESSION AUTHORIZATION postgres; and RESET
> SESSION AUTHORIZATION; would be the same when postgres is the superuser.
> By not using the name of the superuser one get the benefit that one can
> restore as another superuser (but see the part about acl's below).
<snip>
> It's also more complicated since in some cases the acl is set to NULL
> which means that it has the default priviledges. And the default
> privileges always include all privileges for the owner. So if the acl is
> NULL then the old owner looses its privileges and the new gets them. Here
> we have a different semantics based on an implementation detail that's not
> very visible to the user.
<snip>
Chris K-L came on IRC after you logged off last night. Apparently, he's
already fixed all of the above for 8.0. Since I have a "destruction test"
available, I'll see how it does.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2004-10-24 21:07:46 | Compile error on 7.2.6/contrib/seg |
Previous Message | Dennis Bjorklund | 2004-10-24 15:10:37 | Re: [HACKERS] BUG #1290: Default value and ALTER...TYPE |