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 1opogO-0003cL-FW for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Nov 2022 10:39:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1opogN-0002UC-AN for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Nov 2022 10:39:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1opogM-0002U3-Vu for pgsql-hackers@lists.postgresql.org; Tue, 01 Nov 2022 10:39:46 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1opogK-0005Ym-KT for pgsql-hackers@lists.postgresql.org; Tue, 01 Nov 2022 10:39:45 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E902C5C01E8; Tue, 1 Nov 2022 06:39:43 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 01 Nov 2022 06:39:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1667299183; x= 1667385583; bh=nRvO24KToZBQCYPAqFAVUQQ6VtirUlIW4d5jfaOYxHY=; b=M RsjREZEqnsJrVGeyAx+ph9PyBkOmMi22iczSI25w3RGMRGWfFy98ROmNoc3lvC5W uJPpaUF5dTdgbpMGMXdZFA7WExS68r+0kfN5CqrHLgkMwyWA/2q5OGkdWrXPEej6 NmmhlDIa0pb9GcYHwK5YEt+cpceYGDv4+3rF9ReX0bEQwJ5QWsukd4UMzYWWPK1P RIEEz4kFb0MGoiKeE7k0qg7PqNdXbZExVPxszBezVuZon1pTnqDLZr2ooO4Ph6Wf 7cHy25k6zneebzV7Lpk5oC9saiKT8vlEQsbseU+/rObkJaq25fMHHuIrTZ0B/54m VMymBY3eqNXu3w4Sl36TA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrudehgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeetiefh leetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Nov 2022 06:39:41 -0400 (EDT) Message-ID: <9fde5de1-8560-361b-2107-82d617aa2c99@enterprisedb.com> Date: Tue, 1 Nov 2022 11:39:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Subject: Re: real/float example for testlibpq3 Content-Language: en-US To: Mark Wong , Tom Lane Cc: Robert Haas , Greg Stark , Chapman Flack , Ashutosh Bapat , PostgreSQL Hackers References: <2511609.1646061540@sss.pgh.pa.us> <621D4CF3.6090808@anastigmatix.net> <2746817.1646088530@sss.pgh.pa.us> <967228.1655408510@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 01.07.22 19:18, Mark Wong wrote: > Just wanted to do another quick check in before I go too far. How do > does this start look? Extending the libpq section with a code snippet > and description per data type? If we want to start documenting the binary format for all data types, it should go into the "Data Types" chapter. There, we already document the text format in great detail, so putting the binary format in there as well would make sense. The libpq chapter could then contain some examples of applying that information in the context of libpq. But the libpq documentation shouldn't be the primary place where the formats are documented.