> 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.