Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 9DF2F6327B2 for ; Thu, 29 Jan 2009 15:14:59 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 53174-02-6 for ; Thu, 29 Jan 2009 15:14:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by mail.postgresql.org (Postfix) with ESMTP id 23CBE6327B3 for ; Thu, 29 Jan 2009 15:14:32 -0400 (AST) Received: from mailsrv2.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailsrv2.i.zmi.at", Issuer "power4u.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id 471D02C98 for ; Thu, 29 Jan 2009 20:14:29 +0100 (CET) Received: from saturn.localnet (saturn.i.zmi.at [10.0.0.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mailsrv2.i.zmi.at (Postfix) with ESMTPSA id 8757140016F for ; Thu, 29 Jan 2009 20:14:29 +0100 (CET) From: Michael Monnerie Organization: it-management http://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 User-Agent: KMail/1.10.3 (Linux/2.6.27.13-ZMI; KDE/4.1.3; x86_64; ; ) References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com> <7403.1233250794@sss.pgh.pa.us> <4981EB35.5060106@hagander.net> In-Reply-To: <4981EB35.5060106@hagander.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901292014.29195@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/162 X-Sequence-Number: 31209 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