Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Lou Picciano <LouPicciano(at)comcast(dot)net>
Cc: pgsql-testers(at)postgresql(dot)org
Subject: Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...
Date: 2010-06-23 18:01:52
Message-ID: 4C224C10.7080403@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-testers


> *[Results]:* Single Statement approach (#2) always reports ERROR: value
> too long for type character varying(16), even though approach #1 -
> Multiple Inserts - imported exactly the same data with no error. Is the
> single statement approach, with its pre-testing of the query, more
> fastidious? IE, is my data bad, or is this a bug?

I can't reproduce this issue. You'll need to provide a test case. In
other words, I suspect that the data wasn't exactly the same in both cases.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

In response to

Browse pgsql-testers by date

  From Date Subject
Next Message Bruce Momjian 2010-06-23 20:04:22 Re: [TESTERS] R: Postgresql 9.0b2 : pg_upgrade not passing username to pgdumpall ?
Previous Message Josh Berkus 2010-06-23 17:45:42 Re: local_preload_libraries converts path to lowercase?