| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, 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:48:50 |
| Message-ID: | 2746817.1646088530@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Chapman Flack <chap(at)anastigmatix(dot)net> writes:
> 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?
The source code for the type's send/receive functions :-(. One could
wish for something better, but no one has stepped up to produce such
documentation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2022-02-28 22:52:45 | stale statistics on postgres 14 |
| Previous Message | Tom Lane | 2022-02-28 22:46:43 | Re: Separate the result of \watch for each query execution (psql) |