Re: cached plan must not change result type

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>, James Pang <jamespang886(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: Re: cached plan must not change result type
Date: 2024-03-30 14:06:12
Message-ID: 29759a95d5194d1a5a468e2585e363a313c7d287.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-jdbc

On Sat, 2024-03-30 at 08:27 -0400, Dave Cramer wrote:
> > On Fri, 29 Mar 2024 at 19:42, James Pang <jamespang886(at)gmail(dot)com> wrote:
> > > we did DDL "alter table ... alter column increase varchar(512) to varchar(1024)",
> > > after that done, hours later, new query select on this table still failed this error.
> > > From this https://jdbc.postgresql.org/documentation/server-prepare/#re-execution-of-failed-statements ,
> > > looks like pgjdbc try to handle this exception and retry, but in our case, it did not happen.
> > > Could you direct me how to make this retry work?
> > > we only want new transactions,queries work that after the DDL changes. 
>
> I think the best option for you is to turn off server side prepared statements with prepareThreshold=0

An alternative option is to take downtime for DDL and restart the application.
Or to chppse the appropriate data type right away: in your case, that would
have been "text".

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message James Pang 2024-03-31 03:30:35 Re: cached plan must not change result type
Previous Message Dave Cramer 2024-03-30 12:27:07 Re: cached plan must not change result type

Browse pgsql-jdbc by date

  From Date Subject
Next Message James Pang 2024-03-31 03:30:35 Re: cached plan must not change result type
Previous Message Dave Cramer 2024-03-30 12:27:07 Re: cached plan must not change result type