| From: | Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Encoding problem using pg_dumpall |
| Date: | 2009-01-29 19:14:28 |
| Message-ID: | 200901292014.29195@zmi.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Donnerstag 29 Januar 2009 Magnus Hagander wrote:
> Most people use pg_dump. I know I recommend everbody to use pg_dump
> to dump the database, because you can use -Fc. Then just use
> pg_dumpall to dump the globals, and they normally don't have any
> non-ascii in them.
Why couldn't pg_dumpall get the same behaviour as pg_dump? It could get
that -Fc, and couldn't it be implementet as "call pg_dump for each db
and once for the system"? Why is it that different at all?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee Azzarello | 2009-01-29 19:47:14 | Warm standby recovery failure |
| Previous Message | Magnus Hagander | 2009-01-29 17:45:25 | Re: [GENERAL] Encoding problem using pg_dumpall |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rhubbell | 2009-01-29 19:22:26 | Re: Pet Peeves? |
| Previous Message | Greg Smith | 2009-01-29 19:12:45 | Re: Pet Peeves? |