Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id EECC0632A37 for ; Thu, 29 Jan 2009 21:08:05 -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 32757-08 for ; Thu, 29 Jan 2009 21:08:02 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id F340C632487 for ; Thu, 29 Jan 2009 21:08:02 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n0U16flk014709; Thu, 29 Jan 2009 20:06:41 -0500 (EST) To: Michael Monnerie cc: pgsql-admin@postgresql.org Subject: Re: [GENERAL] Encoding problem using pg_dumpall In-reply-to: <200901292014.29195@zmi.at> References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com> <7403.1233250794@sss.pgh.pa.us> <4981EB35.5060106@hagander.net> <200901292014.29195@zmi.at> Comments: In-reply-to Michael Monnerie message dated "Thu, 29 Jan 2009 20:14:28 +0100" Date: Thu, 29 Jan 2009 20:06:41 -0500 Message-ID: <14708.1233277601@sss.pgh.pa.us> From: Tom Lane 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/164 X-Sequence-Number: 31211 Michael Monnerie writes: > 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? 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. regards, tom lane