| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Dominique Devienne" <ddevienne(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: About the stability of COPY BINARY data |
| Date: | 2024-11-07 17:39:02 |
| Message-ID: | 1214b740-22de-4151-a3c8-e93e3385c0da@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dominique Devienne wrote:
> Also, does the code for per-type _send() and _recv() functions
> really change across versions of PostgreSQL? How common are
> instances of such changes across versions? Any examples of such
> backward-incompatible changes, in the past?
For the timestamp types, I think these functions were
sending/expecting float8 (before version 7.3), and then float8 or
int64 depending on the server configuration up until 9.6, and since
then int64 only.
The same for the "time" field of the interval type.
There is still an "integer_datetimes" GUC reflecting this.
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2024-11-07 17:55:03 | Re: About the stability of COPY BINARY data |
| Previous Message | Dominique Devienne | 2024-11-07 17:14:46 | Re: About the stability of COPY BINARY data |