Re: extended query protcol violation?

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: pg(at)fastcrypt(dot)com
Cc: sitnikov(dot)vladimir(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: extended query protcol violation?
Date: 2018-12-08 13:18:38
Message-ID: 20181208.221838.1208394013093527169.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> > Curious what client is this that is violating the protocol.
>>
>> I heard it was a Java program.
>>
>
> This is not surprising there are a proliferation of non-blocking
> implementations,
> probably approaching 10 different implementations now.

Do you think some of the implementations may not be appropriate if
they behave like that discussed in this thread? If so, maybe it is
worth to add a warning to the backend.

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2018-12-08 13:36:08 Re: extended query protcol violation?
Previous Message Amit Kapila 2018-12-08 13:05:20 Re: WIP: Avoid creation of the free space map for small tables