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

Поиск
Список
Период
Сортировка
От Vladimir Sitnikov
Тема Re: Set search_path + server-prepared statements = cached plan must not change result type
Дата
Msg-id CAB=Je-GtFy=Qa1Eku1mgRZ8RabUfqnUE2Z6ye2CJJZNN9B3Odg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Set search_path + server-prepared statements = cached plan must not change result type  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Set search_path + server-prepared statements = cached plan must not change result type  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
>  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 по дате отправления:

Предыдущее
От: Konstantin Knizhnik
Дата:
Сообщение: Re: Proposal for UPDATE: do not insert new tuple on heap if update does not change data
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Proposal for UPDATE: do not insert new tuple on heap if update does not change data