Date: Wed, 9 Nov 2022 12:47:23 -0800
From: Mark Wong <markwkm@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.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>
Subject: Re: real/float example for testlibpq3
Message-ID: <Y2wR2zMVs0mYhXaF@moubin>
References: <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>
 <4f9ad8c2-b3b6-4d09-1e05-57b97ced926e@enterprisedb.com>
 <1991525.1667483722@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1991525.1667483722@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/Y2wR2zMVs0mYhXaF%40moubin>
Precedence: bulk

On Thu, Nov 03, 2022 at 09:55:22AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> > On 01.11.22 09:15, Tom Lane wrote:
> >> 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 said "near", not "in".  At the time I was thinking "new appendix",
> but I now recall that the wire protocol docs are not an appendix
> but a chapter in the Internals division.  So that doesn't seem like
> quite the right place anyway.
> 
> Perhaps a new chapter under "IV. Client Interfaces" is the right
> place?
> 
> If we wanted to get aggressive, we could move most of the nitpicky details
> about datatype text formatting (e.g., the array quoting rules) there too.
> I'm not set on that, but it'd make datatype.sgml smaller which could
> hardly be a bad thing.
> 
> > 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.
> 
> Yup.

I'll take a stab at adding a new chapter and share how that looks.

Regards,
Mark

--
Mark Wong
EDB https://enterprisedb.com