Re: 7.2 changes to varchar truncation - Mailing list pgsql-general

From Tom Lane
Subject Re: 7.2 changes to varchar truncation
Date
Msg-id 14517.1009837389@sss.pgh.pa.us
Whole thread Raw
In response to 7.2 changes to varchar truncation  ("Jeffrey W. Baker" <jwbaker@acm.org>)
List pgsql-general
"Jeffrey W. Baker" <jwbaker@acm.org> writes:
> What do I do to get back the old behavior?

You don't.  Unfortunately, SQL92 specifies the new behavior.

You might think about declaring the columns plain text and using
triggers to do the truncation, if you really want truncation to a
length limit.

> If I have to change my datatypes to text or varchar without a limit, I'll
> have to drop and reload my databases (again), about which I plan to have a
> real bad attitude.

Consider hacking pg_attribute.atttypmod or pg_attribute.atttypid, if the
reload time is too daunting.  (However, if you failed to reload your
data because of this error, it seems like you aren't in position to
avoid a reload anyway...)

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Large Tables/clustering/terrible performance
Next
From: Thomas Lockhart
Date:
Subject: Re: 7.2 changes to varchar truncation