BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite

From: "" <xuan--2009(dot)03--submitbug--support--postgresql(dot)org(at)baldauf(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite
Date: 2009-03-04 01:37:10
Message-ID: 200903040137.n241bAUV035002@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers


The following bug has been logged online:

Bug reference: 4689
Logged by:
Email address:
xuan--2009(dot)03--submitbug--support--postgresql(dot)org(at)baldauf(dot)org
PostgreSQL version: 8.3.5
Operating system: Linux 2.6.18-6-amd64
Description: Expanding the length of a VARCHAR column should not
induce a table rewrite
Details:

Suppose there is a table "sometable" with a column "somecolumn" of type
"VARCHAR(5)".

This table as many rows.

When executing
"ALTER TABLE sometable ALTER COLUMN somecolumn TYPE VARCHAR(7)", the whole
table is re-written, and this rewrite takes many hours. During these hours,
all writers on this table stall, making the database effectively
unavailable.

However, in almost all cases, there is no need for such relaxing of limits
to require a table rewrite.

So the expected run time needed for this statement is about one second, the
actual run time needed for this statement is many hours.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-03-04 10:06:59 Re: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite
Previous Message Tom Lane 2009-03-03 15:57:00 Re: BUG #4688: Bug in cache.

Browse pgsql-hackers by date

  From Date Subject
Next Message Selena Deckelmann 2009-03-04 01:54:54 Make SIGHUP less painful if pg_hba.conf is not readable
Previous Message Alvaro Herrera 2009-03-03 23:33:15 Re: building pg_dump doesn't work