Wire protocol change - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Wire protocol change
Date
Msg-id 20160422.002852.492604485075798451.t-ishii@sraoss.co.jp
Whole thread Raw
Responses Re: Wire protocol change  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
If we are going to change the wire protocol, it would be nice if parse
complete message includes an identification of the previous parse
message. Same thing can be said to bind complete, command complete and
close complete.

The identification could be an either sequence number assigned to the
parse message or just the statement name (IMO sequence numbers are
better since duplicated statement names could be possible).

Background: in extended protocol, a reply to a message sent to server
could be asynchronously returned. This may raise problems with certain
applications which want to track down the reply messages. Suppose we
have:

Parse('q1')
Bind('s1', 'p1')
Execute('p1')
Parse('q2')
Bind('s2', 'p2')
Execute('p2')
Sync

The reply messages would be:

ParseComplete .. (a)
BindComplete
CommandComplete
ParseComplete .. (b)
BindComplete
CommandComplete
ReadyForQuery

Since (a) and (b) are compeletely identical message, it's not easy to
ditinguish which a and b.

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



pgsql-hackers by date:

Previous
From: Andrea Adami
Date:
Subject: Query Procedures
Next
From: "David G. Johnston"
Date:
Subject: Re: Query Procedures