| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Mark Wong <markwkm(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: real/float example for testlibpq3 |
| Date: | 2022-02-28 22:30:11 |
| Message-ID: | 621D4CF3.6090808@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/28/22 10:19, Tom Lane wrote:
>> That will standardize the
>> way to fetch real typed values in libpq. That leads to the next
>> question. Do we need to introduce different PQget*value() for standard
>> C/SQL data types.
>
> ... I do not want to go here. Where would you stop? How would you
> deal with cross-machine inconsistencies in integer widths?
This stimulates a question for me.
Not just libpq, but all drivers implemented in whatever language, if they
wish to support binary protocol, depend on knowing what the committed
send/recv wire formats are for whichever types they mean to support.
In the current state of affairs, what's considered the ur-source of that
information?
I have often seen those formats documented in code comments, usually above
the recv function in the .c file for a given adt.
Have we got any more, well, machine-readable collection of that knowledge?
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-02-28 22:46:43 | Re: Separate the result of \watch for each query execution (psql) |
| Previous Message | Greg Stark | 2022-02-28 22:03:25 | Re: Removing unneeded self joins |