| From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | xuan--2009(dot)03--submitbug--support--postgresql(dot)org(at)baldauf(dot)org, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| Date: | 2009-03-04 10:42:06 |
| Message-ID: | 1d4e0c10903040242w6a7f00c2r73de4d2741065c94@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Mar 4, 2009 at 11:06 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> While this isn't a bug, it's a reasonable feature request. I've added this
> to the TODO page: http://wiki.postgresql.org/wiki/Todo#ALTER
>
> Patches are welcome.
I remember someone proposed a patch for that a long time ago:
http://archives.postgresql.org/pgsql-patches/2006-10/msg00154.php
AFAICS there were 2 possible follow-ups to this patch:
- only manage the case of char/varchar (which is the most common case anyway);
- develop a complete infrastructure to handle all the cases as
suggested by Gregory.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-03-04 10:50:15 | Re: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| Previous Message | vikas | 2009-03-04 10:15:49 | BUG #4690: an select query is not using the index |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-03-04 10:50:15 | Re: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| Previous 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 |