Re: Truncation Problems

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeremy D Carlson <jeremy(at)gustavus(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Truncation Problems
Date: 2001-06-22 15:22:56
Message-ID: 4100.993223376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeremy D Carlson <jeremy(at)gustavus(dot)edu> writes:
> We are having problems with information we are inserting into our
> database being truncated. This information is being inserted via the
> web through Apache 1.3.6 while using ColdFusion 4.0.1's ODBC interface
> into a PostgreSQL 7.0.2 database. It is being truncated in a couple of
> ways. Sometimes, after so many characters, the information is truncated
> in each column. Other times, the information for the last part of the
> insertion string is lost. These insertions usually contain a couple
> paragraphs of information for each column. We haven't had any problem
> with short insertions. Neither ColdFusion nor PostgreSQL return an
> error on a truncation. We occasionally will receive a "query string too
> long" error from PostgreSQL, but no information is actually inserted
> into the database. The query string error is also confusing because
> each column should be able to contain 1+GBs of information.

7.0.2 does not support "1+GBs" per column. You need to update to 7.1.*
to have wide columns.

The error message "query string too long" is also suspicious, since that
string appears nowhere in either current or 7.0 sources. I suspect you
are using obsolete client-side software (left over from 6.5 or before)
that still thinks Postgres has a query length limit.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Lotus Luby-Loo 2001-06-22 15:46:20
Previous Message Jeremy D Carlson 2001-06-22 14:59:56 Truncation Problems