Feedback-ID: i131946ab:Fastmail
Message-ID: <4f9ad8c2-b3b6-4d09-1e05-57b97ced926e@enterprisedb.com>
Date: Thu, 3 Nov 2022 09:23:00 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.4.0
Subject: Re: real/float example for testlibpq3
Content-Language: en-US
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mark Wong <markwkm@gmail.com>, Robert Haas <robertmhaas@gmail.com>,
 Greg Stark <stark@mit.edu>, Chapman Flack <chap@anastigmatix.net>,
 Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <Yhf70G9OYIKueYZi@workstation-mark-wong>
 <CAExHW5tm1FyoLZXdTjdrfRO7ObuoL_p2krc65C5s8D3eWFB50g@mail.gmail.com>
 <2511609.1646061540@sss.pgh.pa.us> <621D4CF3.6090808@anastigmatix.net>
 <2746817.1646088530@sss.pgh.pa.us>
 <CAM-w4HM2t7TonV7bz+V27Vvoo0j6hN9-omDo9SHmQ7O58UFYQg@mail.gmail.com>
 <YqjH9qGaIixfZXQo@workstation-mark-wong>
 <CA+TgmobLR929aHtOfC=JKqz+qzDxdYo_dssj06TyOpnU+HbT6A@mail.gmail.com>
 <967228.1655408510@sss.pgh.pa.us> <Yr8sXL9J/nel7BEM@workstation-mark-wong>
 <9fde5de1-8560-361b-2107-82d617aa2c99@enterprisedb.com>
 <1148727.1667308546@sss.pgh.pa.us>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <1148727.1667308546@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/4f9ad8c2-b3b6-4d09-1e05-57b97ced926e%40enterprisedb.com>
Precedence: bulk

On 01.11.22 09:15, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> 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.
> 
> Agreed that the libpq manual is not the place for this, but I feel
> like it will also be clutter in "Data Types".  Perhaps we should
> invent a new appendix or the like?  Somewhere near the wire protocol
> docs seems sensible.

Would that clutter the protocol docs? ;-)

I suppose figuring out exactly where to put it and how to mark it up, 
etc., in a repeatable fashion is part of the job here.