| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: OWNER TO on all objects |
| Date: | 2004-06-16 13:26:31 |
| Message-ID: | 21244.1087392391@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> 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!
Seems reasonable. The -c option is pretty badly thought out anyway :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-06-16 15:15:42 | Re: Improving postgresql.conf |
| Previous Message | Tom Lane | 2004-06-16 13:24:25 | Re: OWNER TO on all objects |