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

From Lou Picciano
Subject Single-statement INSERT with multiple VALUES clauses behaving strangely...
Date
Msg-id BBC6113D-0AC0-4E67-8E41-11F929888C8B@comcast.net
Whole thread Raw
Responses Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...  (Josh Berkus <josh@agliodbs.com>)
List pgsql-testers
[TEST REPORT]
[Release]: 9.0beta2
[Test Type]: Interface (psql data load testing)
[Test]: Testing various configurations of INSERT syntax, in order to do server load testing.
[Platform]: SUN E450 Quad, Solaris 10.
[Parameters]: Two separate tests, performed as psql imports; ie, dbname=> \i importfile.sql
1) INSERT INTO table VALUES (value0, value1, value2);    vs.
2) INSERT INTO table (field0, field1, field2) VALUES 
(value0, value1, value2),
... 2000 records
(value0, value1, value2);
[Failure]: YES (it would seem..)
[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?
[Comments]: Trying COPY next.

pgsql-testers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: local_preload_libraries converts path to lowercase?
Next
From: "Cassiano, Marco"
Date:
Subject: pg_upgrade fails with "permission denied for relation pg_authid"