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

Add check for constant PGRES_TUPLES_CHUNK to fix compilation failures #17540

Closed
wants to merge 1 commit into from

Conversation

chschneider
Copy link

We have an OpenSUSE 15.6 installation with libpq5 installed (the current version being libpq5-17.2-..., i.e. compatible with postgresql17).
But as the current version of postgis does not work properly with postgresql17 so we are currently stuck with the packages postgresql16 and postgresql16-devel.

The file ext/pgsql/config.m4 only checks for the function PQsetChunkedRowsMode but the header files of postgresql16-devel does not define the constant PGRES_TUPLES_CHUNK in libpq-fe.h which leads to a compilation failure.

I added a check for PGRES_TUPLES_CHUNK to avoid this while keeping the feature enabled if the include file declares the constant.

@devnexen
Copy link
Member

Seems correct thanks, I ll have a look soon-ish. Would you be able to target PHP-8.4 instead ?

@chschneider
Copy link
Author

Seems correct thanks, I ll have a look soon-ish. Would you be able to target PHP-8.4 instead ?

I could do a PR for 8.4, is that preferred to master and then back-porting it? I was under the impression that PRs should be against master but that knowledge is probably outdated

@devnexen
Copy link
Member

devnexen commented Jan 21, 2025

For fixes (inclucing build bugs), we target to the lowest branch the fix applies to. However if it is an issue for you to change target branch, I ll manage at commit time it s fairly small no worries :)

@devnexen
Copy link
Member

Eventually it might be best to redo a proper PR for PHP-8.4 directly.

@chschneider
Copy link
Author

Hmm, changing the target branch seemed to mess up the PR as hundred of changed files were shown. I think it is easier if I leave it at master, no?

Or I could delete the PR and create a new one for 8.4

@devnexen
Copy link
Member

whatever suits you best, I ll review it in few dozen of minutes. Cheers.

Copy link
Member

@devnexen devnexen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nielsdos nielsdos removed request for adoy and bukka January 21, 2025 18:27
@devnexen
Copy link
Member

Thanks !

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