| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Mark Wong <markwkm(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-01 10:39:40 |
| Message-ID: | 9fde5de1-8560-361b-2107-82d617aa2c99@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-11-01 10:55:32 | Re: Commit fest 2022-11 |
| Previous Message | Heikki Linnakangas | 2022-11-01 10:39:39 | Re: ResourceOwner refactoring |