The wire format for infinity/-infinity adds no breaking changes- it is just the various values set to either minimum or maximum possible int64/int32 values.
I attempted to match how InfinityModifier works in other types, such as date and timestamptz.
Please let me know what, if anything, I forgot to update here, and any other feedback is definitely welcome.
It feels like this is relatively safe and backward compatible with older versions, since you can just choose not to use infinity values with older versions, and since there were no wire format changes. However, I'm happy to make changes or documentation updates if that is necessary.
Although Postgres 17 is still in beta, I thought it might make sense to get ahead of one of the changes being made.
Added in this commit: https://github.com/postgres/postgres/commit/519fc1bd9 Upstream release notes: https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-DATATYPES
The wire format for infinity/-infinity adds no breaking changes- it is just the various values set to either minimum or maximum possible int64/int32 values.
I attempted to match how InfinityModifier works in other types, such as date and timestamptz.
Please let me know what, if anything, I forgot to update here, and any other feedback is definitely welcome.
It feels like this is relatively safe and backward compatible with older versions, since you can just choose not to use infinity values with older versions, and since there were no wire format changes. However, I'm happy to make changes or documentation updates if that is necessary.