Re: extended query protcol violation?

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: extended query protcol violation?
Date: 2018-12-08 10:56:49
Message-ID: CAB=Je-FiB_u2FZSpFWZYbq9ToL1pSkiC5UkRnqQ4TYenJt8sGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>Curious what client is this that is violating the protocol.

I stand corrected: that is not a violation, however client might get
unexpected failure of query(begin) in a rare case of close(s1) or close(s2)
fail.

Vladimir

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2018-12-08 12:21:09 docs: outdated reference to recursive expression evaluation
Previous Message Dave Cramer 2018-12-08 10:53:46 Re: extended query protcol violation?