Re: pg_get_triggerdef in pg_dump - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_get_triggerdef in pg_dump
Date
Msg-id 01dc01c33600$bfae31b0$6500a8c0@fhp.internal
Whole thread Raw
In response to Re: pg_get_triggerdef in pg_dump  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
> 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.

Is there demand for an ALTER COLUMN/SET TYPE that is restricted to binary
compatible casts and increasing length changes?

Chris



pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: allowed user/db variables
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_get_triggerdef in pg_dump