X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 03199DB734 for ; Tue, 1 Nov 2005 17:47:18 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 51887-03 for ; Tue, 1 Nov 2005 21:47:15 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by svr1.postgresql.org (Postfix) with ESMTP id 6A148DB72F for ; Tue, 1 Nov 2005 17:47:16 -0400 (AST) Received: (qmail 28647 invoked from network); 1 Nov 2005 21:47:16 -0000 Received: from mail.kinesis-cem.com (HELO pdarley) (kinesis@[64.81.9.230]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Nov 2005 21:47:15 -0000 From: "Peter Darley" To: "Tom Lane" Cc: "Pgsql-Admin" Subject: Re: Can't dump and restore Date: Tue, 1 Nov 2005 13:52:10 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <28422.1130881063@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/14 X-Sequence-Number: 19387 Tom, You're correct, the new database was being created as UNICODE instead of SQL_ASCII. I'd never messed with encoding before, but I guess that the default was changed some time after I originally made the database on 6.x. Stupid mistake. :) Thanks a bundle for your help! Peter Darley -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, November 01, 2005 1:38 PM To: Peter Darley Cc: Pgsql-Admin Subject: Re: [ADMIN] Can't dump and restore "Peter Darley" writes: > So, long and short, I think that everything should be SQL_ASCII, but even > when it is, I get the error. There is no way you're going to get that error if the encoding setting is SQL_ASCII, so better look again. "SHOW server_encoding" and "SHOW client_encoding" might be revealing. regards, tom lane