Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: About the stability of COPY BINARY data
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Dominique Devienne" <ddevienne@gmail.com>
Cc: pgsql-general@postgresql.org
In-Reply-To: <CAFCRh-9W8mXh9MfRe-Z5bAcN5FVbsXuSW60-QPVMB1jHC4+bzQ@mail.gmail.com>
Date: Thu, 07 Nov 2024 18:39:02 +0100
Message-Id: <1214b740-22de-4151-a3c8-e93e3385c0da@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/1214b740-22de-4151-a3c8-e93e3385c0da%40manitou-mail.org>
Precedence: bulk

	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,
--=20
Daniel V=E9rit=E9
https://postgresql.verite.pro/
Twitter: @DanielVerite