Re: [pgadmin-hackers] Fwd: Re: Howto change column

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: [pgadmin-hackers] Fwd: Re: Howto change column
Date: 2001-11-07 18:05:16
Message-ID: 20011107095918.W49377-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 7 Nov 2001, Jean-Michel POURE wrote:

> At 14:46 07/11/01 +0000, you wrote:
> > > >If you're willing to do a little magic to the system tables (and you
> > > >have a recent backup :) ). You can change the atttypmod of
> > > the column
> > > >in question from 14 to 24. This really only works on
> > > variable length
> > > >items and only to expand them, but...
> > > >
> > > >You pretty much need to do a sequence like:
> > > >select oid, relname from pg_class where
> > > relname='<tablename>'; update
> > > >pg_attribute set atttypmod=24 where attrelid=<oid from previous>
> > > > and attname='<attributename>'
> > > >in a superuser account.
> >
> >Though technically correct, that sounds like a recipe for disaster! Of
> >course, the atttypmod doesn't always relate directly to the length of the
> >column, and even when it does, it's usually length+4

For the text types I think it's generally length+4. For numeric, I think
it's precision*65536+scale. The best way to find out is probably to
declare a column of the target type and check.

Of course, the best way to deal with this right now is to dump the
affected tables and reload until drop field is done.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gordan Bobic 2001-11-07 18:10:08 Re: Performance Question Followup No.2
Previous Message Tom Lane 2001-11-07 18:01:12 Re: Old Template0 is annoying me!