Re: Fixing a too long column value in a before insert

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Fixing a too long column value in a before insert
Date: 2005-05-11 14:01:17
Message-ID: 1115820077.22860.69.camel@coppola.muc.ecircle.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)ecircle-ag(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Neil Conway 2005-05-11 14:14:50 Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL
Previous Message Greg Stark 2005-05-11 13:59:05 Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL