| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Reverting SET SESSION AUTHORIZATION command |
| Date: | 2002-02-24 23:35:37 |
| Message-ID: | 13426.1014593737@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> BTW, I think it's well past time to make pg_dump use SET SESSION
>> AUTHORIZATION by default, or even always, instead of \connect commands.
> Well, the tradeoff is "restoring user has to be superuser" vs "restoring
> user has to know everyone's authentication secrets". The former is
> obviously more likely.
Hmm, good point. But we could ease this if the system allowed
"SET SESSION AUTHORIZATION <myself>" to non-superusers. Then a
pg_dump of your own stuff would still restore without trouble.
A pg_dump of multiple people's stuff is superuser territory anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-24 23:47:34 | Re: Duration of beta period |
| Previous Message | Peter Eisentraut | 2002-02-24 23:32:36 | Re: Reverting SET SESSION AUTHORIZATION command |