Re: extended query protcol violation?

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: 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 08:57:02
Message-ID: CAB=Je-Fc5dc885qc9Aq9tOLPKYEDGR6-g4zNam2Kp-ie1DF1nQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo>responses of a simple query do not include CloseComplete

Tatsuo, where do you get the logs from?
I guess you are just confused by the PRINTED order of the messages in the
log.
Note: wire order do not have to be exactly the same as the order in the log
since messages are buffered, then might be read in batches.

In other words, an application might just batch (send all three) close(s2),
close(s1), query(begin) messages, then read the responses.
How does it break protocol?

Vladimir

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2018-12-08 09:48:06 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock
Previous Message Tatsuo Ishii 2018-12-08 08:23:09 Re: extended query protcol violation?