| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mark Wong <markwkm(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Chapman Flack <chap(at)anastigmatix(dot)net>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: real/float example for testlibpq3 |
| Date: | 2022-11-03 13:23:00 |
| Message-ID: | 4f9ad8c2-b3b6-4d09-1e05-57b97ced926e@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01.11.22 09:15, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-11-03 13:26:38 | Re: Pluggable toaster |
| Previous Message | houzj.fnst@fujitsu.com | 2022-11-03 13:06:35 | RE: Perform streaming logical transactions by background workers and parallel apply |