Thread: Single-statement INSERT with multiple VALUES clauses behaving strangely...
[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.
Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...
From
Josh Berkus
Date:
> *[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