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

From Christopher Kings-Lynne
Subject Re: OWNER TO on all objects
Date
Msg-id 40CFEC18.6000705@familyhealth.com.au
Whole thread Raw
In response to Re: OWNER TO on all objects  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: OWNER TO on all objects
List pgsql-hackers
There is one other consideration, and that is that current pg_dump likes 
to set session_auth to user of object before outputting drop command, 
when '-c' is specificed.

I propose that we eliminate that set session_auth as well.  If the user 
running the script is the owner of that object or a superuser, then they 
will be able to drop it.  If they are neither, then the drop will fail, 
but the session_authorization would have failed anyway!

Chris



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: OWNER TO on all objects
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: #postgresql report