Re: Fixing a too long column value in a before insert - Mailing list pgsql-general

From Csaba Nagy
Subject Re: Fixing a too long column value in a before insert
Date
Msg-id 1115820077.22860.69.camel@coppola.muc.ecircle.de
Whole thread Raw
In response to Re: Fixing a too long column value in a before insert trigger or rule  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Searching the archives lead me to this link:
http://archives.postgresql.org/pgsql-general/2001-10/msg01208.php
(I also searched before asking but for the wrong keywords...)

Is that advice still valid ?

I will try in any case :-)

Thanks,
Csaba.


On Wed, 2005-05-11 at 15:44, Tom Lane wrote:
> Csaba Nagy <nagy@ecircle-ag.com> writes:
> > We have a situation where a varchar column was limited to a too small
> > maximum length in the design phase... shit happens, we will fix our db
> > schema in our next database downtime or software version deployment,
> > whichever comes first (we are using 7.4 and on the fly column type
> > change is only from 8.0 on I guess).
>
> Why don't you just hack the column's atttypmod?  See the archives
> (and practice on a test database ;-))
>
>             regards, tom lane


pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL
Next
From: Neil Conway
Date:
Subject: Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL