On Tue, Feb 3, 2009 at 1:30 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Phoenix Kiula <phoenix.kiula@xxxxxxxxx> 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? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
