Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 758C0632729; Thu, 29 Jan 2009 13:40:03 -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 46425-01-4; Thu, 29 Jan 2009 13:39:59 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 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 F4199632730; Thu, 29 Jan 2009 13:39:58 -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 n0THdstC007405; Thu, 29 Jan 2009 12:39:54 -0500 (EST) To: Magnus Hagander cc: Moshe Ben-Shoham , pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] Encoding problem using pg_dumpall In-reply-to: <4981E805.7040302@hagander.net> References: <75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com> <28817.1233242176@sss.pgh.pa.us> <4981E805.7040302@hagander.net> Comments: In-reply-to Magnus Hagander message dated "Thu, 29 Jan 2009 18:31:49 +0100" Date: Thu, 29 Jan 2009 12:39:54 -0500 Message-ID: <7403.1233250794@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/160 X-Sequence-Number: 31207 Magnus Hagander writes: > Tom Lane wrote: >> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch, >> which seems like an oversight. So you need to fix your locale, >> or else use pg_dump directly.) > IIRC, you can't set the windows console to be UTF8. Ugh. That seems to raise the priority of having a -E switch quite a lot. I'm surprised no one has complained of this before. I think it should be possible to work around it by setting PGCLIENTENCODING in the environment, but I dunno how to do that on Windows. regards, tom lane