| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Rich Cullingford <rculling(at)sysd(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Moving a database AND changing the superuser |
| Date: | 2003-12-16 13:10:12 |
| Message-ID: | 200312161410.12334.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Rich Cullingford wrote:
> Well, I was gonna use pg_dumpall to avoid the tedium of individual
> dumps, but (gotcha!) pg_dumpall doesn't accept
> --use-set-session-authorization (tho' it does run pg_dump!).
It supplies that option automatically.
> If I use
> pg_dumpall, will pg_restore (with --use-set-session-authorization) be
> smart enough to ignore the \connect calls in the dump?
pg_dumpall output cannot be restored with pg_restore.
> I would try all this stuff myself, but unfortunately my PG 7.4
> machine isn't available yet, so I'm grasping at straws...
In PG 7.4, --use-set-session-authorization is the default and only
option.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-12-16 15:01:26 | Re: Postgresql on software RAID |
| Previous Message | Adam Witney | 2003-12-16 10:52:06 | Postgresql on software RAID |