Skip site navigation (1) Skip section navigation (2)

pg_dump 8.1.2 with 7.4.2 server screws up with LATIN1 strings

From: Marinos Yannikos <mjy(at)geizhals(dot)at>
To: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: pg_dump 8.1.2 with 7.4.2 server screws up with LATIN1 strings
Date: 2006-04-26 23:17:01
Message-ID: (view raw or whole thread)
Lists: pgsql-bugs
I did this:

pg_dump -Fp -a -d -h <server> logdb -t fatlog > fatlog.txt

The output begins with:

SET client_encoding = 'LATIN1';
SET check_function_bodies = false;
SET client_min_messages = warning;

SET search_path = public, pg_catalog;

-- Data for Name: fatlog; Type: TABLE DATA; Schema: public; Owner: root


Now, whenever there is an "Umlaut" character in the strings, the output 
looks like this:

'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)',
302, 352, NULL, 'GET', '', '2006-04-24 18:12:08+02', 
'', '8001
', '', 0, NULL, NULL);

The "\\xfc" in the output apparently causes pg_dump to write an "E" 
before the string in the parentheses, causing the following error during 
execution of the INSERT:

ERROR:  type "e" does not exist

I'm not sure whether the "\\xfc" sequence was in the database like this 
before the dump, it may have been a LATIN1 character or the escape sequence.

Dipl.-Ing. Marinos Yannikos, CEO
Preisvergleich Internet Services AG
Obere Donaustrasse 63, A-1020 Wien
Tel./Fax: (+431) 5811609-52/-55

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2006-04-27 02:41:48
Subject: Re: prepare-alter-exec issue
Previous:From: Anjali AroraDate: 2006-04-26 05:10:54
Subject: Error in returning setof records

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group