| From: | Divya Jain <dijain(at)cisco(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | modifying VARCHAR max length |
| Date: | 2003-05-28 18:35:47 |
| Message-ID: | 4.3.2.7.2.20030528112658.03049288@mira-sjc5-5.cisco.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
I'm running Postgres 7.2.4. A VARCHAR column in my schema needs to be longer than the currently defined max length. What is the best way to achieve this without adding a new column with the correct VARCHAR length ?
One way I figured is to modify the pg_attribute table and set atttypmod to the correct value. Just want to know if there is any risk involved in doing this.
Thanks
Divya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tiago R. Mello | 2003-05-28 19:19:15 | LC_COLLATE - initdb |
| Previous Message | Robert Treat | 2003-05-28 18:24:05 | Re: Perl Book |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | valerian | 2003-05-28 18:36:10 | CURRENT_DATE and CURRENT_TIME return incorrect values |
| Previous Message | Richard Huxton | 2003-05-28 18:09:01 | Re: Lock table |