Re: Slowness of extended protocol

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: sitnikov(dot)vladimir(at)gmail(dot)com, roji(at)roji(dot)org, pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de, stark(at)mit(dot)edu, ishii(at)postgresql(dot)org, robertmhaas(at)gmail(dot)com
Subject: Re: Slowness of extended protocol
Date: 2016-08-08 22:56:09
Message-ID: 20160809.075609.1857962255660550562.t-ishii@sraoss.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> On the other hand, usage of some well-defined statement name to trigger
>> the special case would be fine: all pgbouncer versions would pass those
>> parse/bind/exec message as if it were regular messages.
>
> I do not accept this idea that retroactively defining special semantics
> for certain statement names is not a protocol break. If it causes any
> change in what the server's response would be, then it is a protocol
> break.

+1. It definitely is a protocol break.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-08 23:33:57 Re: dsm_unpin_segment
Previous Message Thomas Munro 2016-08-08 22:15:24 dsm_unpin_segment