Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e974eEJ83448 for ; Sat, 7 Oct 2000 00:40:14 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e974eAB18228; Sat, 7 Oct 2000 00:40:10 -0400 (EDT) To: Randy Jonasz cc: "Clark, Joel" , Adam Haberlach , Postgres Interfaces Subject: Re: C++ interfaces In-reply-to: References: Comments: In-reply-to Randy Jonasz message dated "Fri, 06 Oct 2000 18:26:36 -0400" Date: Sat, 07 Oct 2000 00:40:10 -0400 Message-ID: <18225.970893610@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/30 Randy Jonasz writes: > I'm currently looking at the packet structures that the back-end and > clients must use. I've found that many packets are terminated with > 0x5A. The docs don't mention this so I was wondering if anyone could > suggest why. I suspect you are confusing the logically-separate ReadyForQuery message (which is a single byte 'Z') with the preceding data message. See http://www.postgresql.org/docs/postgres/protocol.htm, particularly the description of the basic Query cycle: : A Query cycle is initiated by the frontend sending a Query message to : the backend. The backend then sends one or more response messages : depending on the contents of the query command string, and finally a : ReadyForQuery response message. ReadyForQuery informs the frontend that : it may safely send a new query or function call. regards, tom lane