Re: pg_get_triggerdef in pg_dump - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_get_triggerdef in pg_dump
Date
Msg-id 20030618143537.GB2460@dcc.uchile.cl
Whole thread Raw
In response to Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
Responses Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
List pgsql-hackers
On Wed, Jun 18, 2003 at 12:59:36PM +0200, Andreas Pflug wrote:

> What I need again and again, is changing the size of a column (rarely 
> the type). For pgsql, I'd have to drop the column, and need to recreate 
> all views. For MSSQL, it won't matter if the column is dropped/recreated 
> or just resized, the view won't notice until it's used again.

If that's what you need you can always change the system catalogs
manually.  For CHAR(n) and VARCHAR(n) you change pg_attribute.atttypmod
to (n+4).  For NUMERIC(n,m) it's something like (n<<16) + m + 4 or maybe
(m<<16) + n + 4, don't remember right now.

Be sure to check that your data is in a safe place before you do this,
and double check before you commit the transaction if you do it
manually.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Porque Kim no hacia nada, pero, eso si,
con extraordinario exito" ("Kim", Kipling)


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: O_DIRECT in freebsd
Next
From: Rod Taylor
Date:
Subject: Re: lots of configure failures on freebsd/alpha