pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joachim Trinkwitz <jtr@uni-bonn.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problems with pg_dump (on Debian i386)
Date: Mon, 28 May 2001 13:47:00 -0400
Message-ID: <13609.991072020@sss.pgh.pa.us> (raw)
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>

Joachim Trinkwitz <jtr@uni-bonn.de> 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



view thread (4+ messages)

Message-ID: <13609.991072020@sss.pgh.pa.us>
Permalink:  ../13609.991072020@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13609.991072020@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jtr@uni-bonn.de
  Subject: Re: Problems with pg_dump (on Debian i386)
  In-Reply-To: <13609.991072020@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox