Postgres Pro
Downloads
Home   >   mailing lists

Re: Set search_path + server-prepared statements = cached plan must not change result type - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: Set search_path + server-prepared statements = cached plan must not change result type
Date
Msg-id CAB=Je-GtFy=Qa1Eku1mgRZ8RabUfqnUE2Z6ye2CJJZNN9B3Odg@mail.gmail.com
Whole thread Raw
In response to Re: Set search_path + server-prepared statements = cached plan must not change result type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Set search_path + server-prepared statements = cached plan must not change result type  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
>  I believe, and the conclusion was that
>if you think you need this, you're doing it wrong

So what is the recommended approach to use server-prepared statements
at the client side (I mean at JDBC driver side)?

Currently "prepare, switch search_path, execute" leads to "cached plan
must not change result type" error.
Can one expect the issue to be fixed in subsequent 8.4, 8.5, ..., 9.5 versions?

Vladimir

pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Proposal for UPDATE: do not insert new tuple on heap if update does not change data
Next
From: Tom Lane
Date:
Subject: Re: Proposal for UPDATE: do not insert new tuple on heap if update does not change data