Re: OWNER TO on all objects - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: OWNER TO on all objects
Date
Msg-id 40D0F944.1010808@familyhealth.com.au
Whole thread Raw
In response to Re: OWNER TO on all objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>I worded that badly.  I meant "allow a user to change the owner of 
>>something to what it already is".  ie. Just make the no-op allowed by 
>>everyone.  session_auth already does this.
> 
> 
> Ah.  Okay, no objection to that.  (In fact I believe we put in the
> special case for session_auth for exactly the same reason.)

Actually, do I make it that anyone can do a no-op user change, or can 
only the user who is the existing owner do the no-op?  It's a very tiny 
different and probably won't make much difference but perhaps it's 
better to make it a bit tighter check?  What do you think?

Chris



pgsql-hackers by date:

Previous
From: david@fetter.org (David Fetter)
Date:
Subject: Re: PlPerlNG - first alpha code
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: OWNER TO on all objects