| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Matteo Beccati <php(at)beccati(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| Date: | 2009-03-05 19:49:48 |
| Message-ID: | 3073cc9b0903051149u48fe52f3m806b060c14c1f74f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, Mar 5, 2009 at 2:46 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>
>> now, back to the problem... is not easier to define a column as TEXT
>> and to put a check to constraint the length? if you wanna change the
>> constraint that will be almost free
>
> Thanks for the interesting suggestion. I'm not sure I'd want to go
> there for various reasons; but even if I wanted to go that route, how
> would I modify that constraint without causing the whole table to be
> scanned for compliance?
>
the table will be scanned but not rewritten
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-03-05 19:55:59 | Re: Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| Previous Message | Kevin Grittner | 2009-03-05 19:46:22 | Re: Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-05 19:50:24 | Re: SIGHUP during recovery |
| Previous Message | André Volpato | 2009-03-05 19:47:58 | Re: cbrt() broken in AIX |