Re: [GENERAL] Encoding problem using pg_dumpall - Mailing list pgsql-admin

From Michael Monnerie
Subject Re: [GENERAL] Encoding problem using pg_dumpall
Date
Msg-id 200901292014.29195@zmi.at
Whole thread Raw
In response to Re: [GENERAL] Encoding problem using pg_dumpall  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [GENERAL] Encoding problem using pg_dumpall  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
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


pgsql-admin by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
Next
From: Lee Azzarello
Date:
Subject: Warm standby recovery failure