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

Tests are broken after PG17 release #886

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

arajkumar
Copy link
Contributor

@arajkumar arajkumar commented Oct 3, 2024

We do not pin the postgresql-client causing the test failures after PG17 release due to the issue discussed here in the PG mailing list[1].

I think there are other issues related to b0e96f3119 (Catalog not-null
constraints) - if I dump a v16 server using v17 tools, the backup can't
be restored into the v16 server. I'm okay ignoring a line or two like
'unrecognized configuration parameter "transaction_timeout", but not
'syntax error at or near "NO"'.

This commit pins the postgresql-client version as per the docker env variable PGVERSION.

[1] https://postgrespro.com/list/thread-id/2693550

We do not pin the postgresql-client causing the test failures after PG17
release due to the issue discussed here in the PG mailing list[1].

This commit pins the postgresql-client version as per the docker env variable PGVERSION.

[1] https://postgrespro.com/list/thread-id/2693550

Signed-off-by: Arunprasad Rajkumar <[email protected]>
@dimitri dimitri self-requested a review October 3, 2024 14:13
@dimitri dimitri added this to the v0.18 milestone Oct 3, 2024
@dimitri dimitri merged commit 9031626 into dimitri:main Oct 3, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants