From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
Date: Thu, 29 Jan 2009 20:14:28 +0100
Message-ID: <200901292014.29195@zmi.at> (raw)
In-Reply-To: <4981EB35.5060106@hagander.net>
References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com>
<7403.1233250794@sss.pgh.pa.us>
<4981EB35.5060106@hagander.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: michael.monnerie@is.it-management.at
Subject: Re: [GENERAL] Encoding problem using pg_dumpall
In-Reply-To: <200901292014.29195@zmi.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox