Re: NOT EXIST for PREPARE

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: NOT EXIST for PREPARE
Дата
Msg-id CAMsr+YF7-MN4weqjLUmWksP6DRxpaAMVsDZsfMAeM8WfNoME0g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: NOT EXIST for PREPARE  (Yury Zhuravlev <u.zhuravlev@postgrespro.ru>)
Ответы Re: NOT EXIST for PREPARE  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Список pgsql-hackers
On 24 March 2016 at 20:03, Yury Zhuravlev <u.zhuravlev@postgrespro.ru> wrote:
I have a big question. What need to do with message protocol?
If we write name in Parse message we store prepared statement. I see some solutions for this problem but all not ideal:
1. We can add second char token for parse message. But too serious change. 2. We can try add parameter to tail of message. But in tail we have variable length array with parameters. 3. Detect prefix of prepared name. For example "__". Effects think clear.

I really, really doubt you can change this before we do a protocol version bump. The current protocol is too inflexible and doesn't have any kind of capabilities negotiation. I don't think any of those options can work. 


--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Emre Hasegeli
Дата:
Сообщение: Re: [PATCH] we have added support for box type in SP-GiST index
Следующее
От: Robbie Harwood
Дата:
Сообщение: Re: BUG #13854: SSPI authentication failure: wrong realm name used