| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>, "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_get_triggerdef in pg_dump |
| Date: | 2003-06-19 01:18:50 |
| Message-ID: | 01dc01c33600$bfae31b0$6500a8c0@fhp.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-06-19 01:22:03 | Re: pg_get_triggerdef in pg_dump |
| Previous Message | Andreas Pflug | 2003-06-18 22:19:54 | Re: allowed user/db variables |