| From: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <aklaver(at)comcast(dot)net>, Ian Barwick <barwick(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Smartest way to resize a column? |
| Date: | 2009-02-03 06:37:10 |
| Message-ID: | e373d31e0902022237g7a4e6722m2c6692f9349c024e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 3, 2009 at 1:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> writes:
>> Tom, this has worked, and a "\d TABLENAME" shows that the column is
>> varchar(35).
>
>> But I still have messages in my log saying:
>> ERROR: value too long for type character varying(20)
>
> Cached plans maybe?
>
> regards, tom lane
>
Could be. How should I circumvent them? The table is being vacuum
analyzed every hour. Why are the plans cached?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2009-02-03 07:33:53 | Re: Smartest way to resize a column? |
| Previous Message | Owen Hartnett | 2009-02-03 06:18:36 | libpq on iPhone? |