From: | Matteo Beccati <php(at)beccati(dot)com> |
---|---|
To: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, 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: [HACKERS] Re: BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
Date: | 2009-03-05 15:47:30 |
Message-ID: | 49AFF412.7030506@beccati.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Guillaume Smet ha scritto:
> 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.
I recently had a similar problem when I added some domains to the
application. ALTER TABLE ... TYPE varchar_dom was leading to a full
table rewrite even though the underlying type definition were exactly
the same (i.e. varchar(64)). I can live with it, but I suppose this fix
might be related to the varlen one.
Cheers
--
Matteo Beccati
OpenX - http://www.openx.org
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-03-05 19:15:26 | Re: Expanding the length of a VARCHAR column should not induce a table rewrite |
Previous Message | Anamika Saini | 2009-03-05 10:33:37 | Problem in installing postgreSQL in silent mode |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-05 15:54:33 | Re: [BUG] Column-level privileges on inherited tables |
Previous Message | Teodor Sigaev | 2009-03-05 15:26:48 | Re: Review: B-Tree emulation for GIN |