MIME-Version: 1.0
From: James Pang <jamespang886@gmail.com>
Date: Fri, 29 Mar 2024 10:05:59 +0800
Message-ID: 
 <CAHgTRfcg2jGnjSqq1NVuMDtCjRU3aOXWrhXn1L=92Ka_Ug6euw@mail.gmail.com>
Subject: cached plan must not change result type
To: pgsql-admin@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000523b060614c3154c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAHgTRfcg2jGnjSqq1NVuMDtCjRU3aOXWrhXn1L%3D92Ka_Ug6euw%40mail.gmail.com>
Precedence: bulk

--000000000000523b060614c3154c
Content-Type: text/plain; charset="UTF-8"

hi,
   PGV14, client use PGJDBC driver and prepared statements, when a table
"alter table alter column type ..." changes done, a lot of JDBC clients got
this error "cached plan must not change result type".  when a JDBC client
got this error first time after the DDL schema change, JDBC driver will
clear this caching-plan and following same SQL statement got parsing again
and new cached plan right?
  How to avoid this issue when DDL schema changes ?

Thanks,

James

--000000000000523b060614c3154c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">hi,<div>=C2=A0 =C2=A0PGV14, client use PGJDBC driver and p=
repared statements, when a table &quot;alter table alter column type ...&qu=
ot; changes done, a lot of JDBC clients got this error &quot;cached plan mu=
st not change result type&quot;.=C2=A0 when a JDBC client got this error fi=
rst time after the DDL schema change, JDBC driver will clear this caching-p=
lan and following same SQL statement got parsing again and new cached plan =
right?=C2=A0=C2=A0</div><div>=C2=A0 How to avoid this issue when DDL schema=
 changes ?=C2=A0</div><div><br></div><div>Thanks,</div><div><br></div><div>=
James</div></div>

--000000000000523b060614c3154c--