Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.

Поиск
Список
Период
Сортировка
От Tatsuo Ishii
Тема Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.
Дата
Msg-id 20140918.092913.190358543610096443.t-ishii@sraoss.co.jp
обсуждение исходный текст
Ответ на Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
>> I have a hard time believing this. Are we really believing that there's
>> a significant number of clients preparing whitespace?
>
> I don't know about "significant number", but the case is specifically
> called out as legal in the FE/BE protocol spec, for example here:
>
>    Therefore, an Execute phase is always terminated by the appearance of
>    exactly one of these messages: CommandComplete, EmptyQueryResponse
>    (if the portal was created from an empty query string), ErrorResponse,
>    or PortalSuspended.
>
> If we change it, that's a protocol break, and I don't think that being a
> tad cleaner is sufficient argument for that.

Agreed. Thinking about that the simple protocol allows to use an empty
query string, there's no reason to not allow it for the extended protocol.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.
Следующее
От: Alexey Klyukin
Дата:
Сообщение: Re: BUG #11444: autovacuum stuck for 5 days and waits on a lock