| From: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Adrian Klaver" <aklaver(at)comcast(dot)net>, "Ian Barwick" <barwick(at)gmail(dot)com>, "PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Smartest way to resize a column? |
| Date: | 2009-01-12 06:42:55 |
| Message-ID: | e373d31e0901112242q122e3290odb463b3d5aa66ad8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> ALTER COLUMN TYPE is intended for cases where actual transformation of
> the data is involved. Obviously varchar(20) to varchar(35) doesn't
> really require any per-row effort, but there's no operation in the
> system that handles that case. But if you're brave, you can do it
> via manipulation of the system catalogs. Observe:
...snip....
Thanks Tom. Yes, no data change is required. But I don't think I have
the understanding to try what you suggested. Running the alter table
on my home database (almost same data) took an hour and it wasn't
complete. I had even dropped the index. So I guess altering it that
way is a pain in PGSQL. Bummer.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2009-01-12 06:48:55 | Data comparison SQL in PG 8.2.9 |
| Previous Message | Tom Lane | 2009-01-12 05:02:36 | Re: Smartest way to resize a column? |