Postgres Pro
Downloads
Home   >   mailing lists

Re: "Cached plan must not change result type" error whenswitching search_path via explicit execution of SET SEARCH_PATH = ... - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: "Cached plan must not change result type" error whenswitching search_path via explicit execution of SET SEARCH_PATH = ...
Date
Msg-id CAB=Je-ESngGfwRVw-LN7-C27UjBv7tNSPM+3cTtgMVzOnCVARg@mail.gmail.com
Whole thread Raw
In response to [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...  ("Al Presseller" <apresseller@commoninf.com>)
Responses Re: "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...
List pgsql-jdbc
Tree view
That's unfortunate.

Would you please report that ustream? (I mean to the postgresql developers)

The thing is it would be so much easier if pgjdbc would not have to parse SQL in order to identify if the statement was "set search_path".

In the mean time: is lowercase style fine for you?

Vladimir

ср, 25 янв. 2017 г. в 1:27, Al Presseller <apresseller@commoninf.com>:

The fix for issue #496 ("Cached plan must not change result type" when using PreparedStatement cache across schemas) doesn’t work when the default schema is being assigned via explicit execution of a SET statement that renders the search_path keyword in UPPER CASE.   

 

pgsql-jdbc by date:

Previous
From: "Al Presseller"
Date:
Subject: [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...
Next
From: "Al Presseller"
Date:
Subject: Re: [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...