pg.ddx.io  pgsql-testers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Single-statement INSERT with multiple VALUES clauses behaving strangely...
2+ messages / 2 participants
[nested] [flat]

* Single-statement INSERT with multiple VALUES clauses behaving strangely...
@ 2010-06-21 21:16 Lou Picciano <LouPicciano@comcast.net>
  2010-06-23 18:01 ` Re: Single-statement INSERT with multiple VALUES clauses behaving strangely... Josh Berkus <josh@agliodbs.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Lou Picciano @ 2010-06-21 21:16 UTC (permalink / raw)
  To: 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.=

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Single-statement INSERT with multiple VALUES clauses behaving strangely...
  2010-06-21 21:16 Single-statement INSERT with multiple VALUES clauses behaving strangely... Lou Picciano <LouPicciano@comcast.net>
@ 2010-06-23 18:01 ` Josh Berkus <josh@agliodbs.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Josh Berkus @ 2010-06-23 18:01 UTC (permalink / raw)
  To: Lou Picciano <LouPicciano@comcast.net>; +Cc: 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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2010-06-23 18:01 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-06-21 21:16 Single-statement INSERT with multiple VALUES clauses behaving strangely... Lou Picciano <LouPicciano@comcast.net>
2010-06-23 18:01 ` Josh Berkus <josh@agliodbs.com>

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