Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOopl-0001sA-3l for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Feb 2022 22:49:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nOopk-00017y-0n for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Feb 2022 22:49:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOopj-00017o-NI for pgsql-hackers@lists.postgresql.org; Mon, 28 Feb 2022 22:49:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOoph-0000n0-Kd for pgsql-hackers@lists.postgresql.org; Mon, 28 Feb 2022 22:49:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 21SMmoK42746818; Mon, 28 Feb 2022 17:48:50 -0500 From: Tom Lane To: Chapman Flack cc: Ashutosh Bapat , Mark Wong , PostgreSQL Hackers Subject: Re: real/float example for testlibpq3 In-reply-to: <621D4CF3.6090808@anastigmatix.net> References: <2511609.1646061540@sss.pgh.pa.us> <621D4CF3.6090808@anastigmatix.net> Comments: In-reply-to Chapman Flack message dated "Mon, 28 Feb 2022 17:30:11 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2746816.1646088530.1@sss.pgh.pa.us> Date: Mon, 28 Feb 2022 17:48:50 -0500 Message-ID: <2746817.1646088530@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Chapman Flack writes: > This stimulates a question for me. > Not just libpq, but all drivers implemented in whatever language, if they > wish to support binary protocol, depend on knowing what the committed > send/recv wire formats are for whichever types they mean to support. > In the current state of affairs, what's considered the ur-source of that > information? The source code for the type's send/receive functions :-(. One could wish for something better, but no one has stepped up to produce such documentation. regards, tom lane