Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4SI2hA72349 for ; Mon, 28 May 2001 14:02:43 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4SHl0R13612; Mon, 28 May 2001 13:47:00 -0400 (EDT) To: Joachim Trinkwitz cc: pgsql-sql@postgresql.org Subject: Re: Problems with pg_dump (on Debian i386) In-reply-to: <878zjhstyv.fsf@wabe.germanistik.uni-bonn.de> References: <87vgmp5yfd.fsf@waffel.germanistik.uni-bonn.de> <5080.990800971@sss.pgh.pa.us> <878zjhstyv.fsf@wabe.germanistik.uni-bonn.de> Comments: In-reply-to Joachim Trinkwitz message dated "28 May 2001 11:28:40 +0200" Date: Mon, 28 May 2001 13:47:00 -0400 Message-ID: <13609.991072020@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/302 X-Sequence-Number: 3143 Joachim Trinkwitz writes: > CREATE TABLE "lplan" ( > ... > "art" character[] NOT NULL, I believe that PG 7.1 interprets that field declaration as "art" character(1)[] NOT NULL, and then truncates your input to match. 7.2-to-be rejects the input with complaints like psql:germdb.sql:20: ERROR: value too long for type character(1) which is the SQL-specified behavior for char(n) fields. Since you appear to be using different string lengths in your data, I doubt char(n) is the right datatype to begin with. I suggest "art" varchar(n)[] NOT NULL, for some appropriate n. regards, tom lane