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

From: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, xuan--2009(dot)03--submitbug--support--postgresql(dot)org(at)baldauf(dot)org, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite
Date: 2009-03-04 10:57:17
Message-ID: 1d4e0c10903040257n70e5dfe6wd436caae3bc4ec8e@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:50 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> The question is how you want to implement this in a data type independent
> fashion.  You can't assume that increasing the typmod is a noop for all data
> types.

Sure. See my previous answer on -hackers (I don't think this
discussion belong to -bugs) and especially the discussion in the
archives about Jonas' patch.

--
Guillaume

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-03-04 12:13:32 Re: BUG #4688: Bug in cache.
Previous Message Peter Eisentraut 2009-03-04 10:51:05 Re: BUG #4690: an select query is not using the index

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-03-04 11:01:34 Re: Immediate shutdown and system(3)
Previous 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