Postgres Pro
Downloads
Home   >   mailing lists

Re: Cases where alter table set type varchar(longer length) still needs table rewrite - Mailing list pgsql-general

From Tom Lane
Subject Re: Cases where alter table set type varchar(longer length) still needs table rewrite
Date
Msg-id 573.1581949272@sss.pgh.pa.us
Whole thread Raw
In response to Cases where alter table set type varchar(longer length) still needstable rewrite  (Jeremy Finzel <finzelj@gmail.com>)
Responses Re: Cases where alter table set type varchar(longer length) stillneeds table rewrite  (Jeremy Finzel <finzelj@gmail.com>)
List pgsql-general
Tree view 
Jeremy Finzel <finzelj@gmail.com> writes:
> I have a table foo with 100 million rows, and a column:
>    - id character varying(20)
> The following command is the one that we expect to execute very quickly (we
> are not seeing any locking), but it is instead taking a very long time:
>    - ALTER TABLE foo ALTER COLUMN id TYPE varchar(100);

Hm, the code is supposed to avoid a table rewrite, but I wonder if
there's something else that's not being avoided, such as an index
rebuild or foreign-key verification.  Could we see the whole table
definition, eg from psql \d+ ?

            regards, tom lane

pgsql-general by date:

Previous
From: Jeremy Finzel
Date:
Subject: Cases where alter table set type varchar(longer length) still needstable rewrite
Next
From: Jeremy Finzel
Date:
Subject: Re: Cases where alter table set type varchar(longer length) stillneeds table rewrite