Re: Single-statement INSERT with multiple VALUES clauses behaving strangely... - Mailing list pgsql-testers

From Josh Berkus
Subject Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...
Date
Msg-id 4C224C10.7080403@agliodbs.com
Whole thread Raw
In response to Single-statement INSERT with multiple VALUES clauses behaving strangely...  (Lou Picciano <LouPicciano@comcast.net>)
List 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

pgsql-testers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: local_preload_libraries converts path to lowercase?
Next
From: Bruce Momjian
Date:
Subject: Re: R: [ADMIN] Postgresql 9.0b2 : pg_upgrade not passing username to pgdumpall ?