Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure PostgreSQL 16 compatibility #776

Merged
merged 6 commits into from
Nov 9, 2023
Merged

Ensure PostgreSQL 16 compatibility #776

merged 6 commits into from
Nov 9, 2023

Conversation

feikesteenbergen
Copy link
Member

DateTimeParseError: PostgreSQL source code documents that we can pass null pointers here:

extra can be NULL if not needed for the particular dterr value.
[...]
If escontext points to an ErrorSaveContext node, that is filled instead
of throwing an error

DecodeDateTime however does not allow us to pass a null pointer, reading the source code, it is expected that extra is not null. Therefore, in order for us to get this thing to compile, we create an empty DateTimeErrorExtra, which gets passed along.

DateTimeParseError: PostgreSQL source code documents that we can pass
null pointers here:

 > extra can be NULL if not needed for the particular dterr value.
 > [...]
 > If escontext points to an ErrorSaveContext node, that is filled instead
 > of throwing an error

DecodeDateTime however does not allow us to pass a null pointer, reading
the source code, it is expected that extra is not null. Therefore, in
order for us to get this thing to compile, we create an empty
DateTimeErrorExtra, which gets passed along.
@feikesteenbergen
Copy link
Member Author

The CI image was built here. We still need to merge that PR in the release build scripts repo.

To achieve this, we have had to change quite a few things:

Explicitly list our Docker Image builds

The logic in the json was pretty complex, by using more yamls, and lists
we hope to achieve a workflow that is easier to inspect, reason with and
adapt.

We also need to reintroduce the difference between $PG_VERSIONS and
$TSDB_PG_VERSIONS, as PostgreSQL 16 support is not yet available for
TimescaleDB.
@syvb
Copy link
Member

syvb commented Oct 23, 2023

I pushed commits to get the CI closer to passing - timescale/timescaledb#6077 broke some of the tests when it introduced a breaking change to TimescaleDB.

@feikesteenbergen
Copy link
Member Author

bors r+

@syvb syvb added this pull request to the merge queue Nov 9, 2023
@syvb syvb removed this pull request from the merge queue due to the queue being cleared Nov 9, 2023
@syvb
Copy link
Member

syvb commented Nov 9, 2023

Merging this manually since the main bors instance is gone.

@syvb syvb merged commit 91b9bf8 into main Nov 9, 2023
18 checks passed
@syvb syvb deleted the feike/pg16 branch November 13, 2023 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants