Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 10458632C2F for ; Fri, 30 Jan 2009 07:23:58 -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 74691-02 for ; Fri, 30 Jan 2009 07:23:54 -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 3C0C4632C2A for ; Fri, 30 Jan 2009 07:23:53 -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 D4DC9300E for ; Fri, 30 Jan 2009 12:23:49 +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 17D4C40016F for ; Fri, 30 Jan 2009 12:23:50 +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: Fri, 30 Jan 2009 12:23:49 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.27.13-ZMI; KDE/4.1.3; x86_64; ; ) References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com> <200901292014.29195@zmi.at> <14708.1233277601@sss.pgh.pa.us> In-Reply-To: <14708.1233277601@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901301223.49703@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/167 X-Sequence-Number: 31214 On Freitag 30 Januar 2009 Tom Lane wrote: > The -Fc (and -Ft) formats are only designed to hold the contents of a > single database; and pg_restore only knows how to restore into a > single database. > > If you feel like fixing that, step right up. Sorry, didn't want to step on toes here. I know that sometimes if you perfectly know a system you get blind over alternatives, and wanted to throw in an idea. The format of pg_dumpall could be a tar of single pg_dumps as well, making pg_dumpall just call pg_dump for each db, putting that output into the tar output from pg_dumpall. But again, just an idea, I don't mind really. I'm just a sysadmin who wants things as easy as possible. Maybe fixing pg_dumpall to include that -E is easier. 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