build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI- breaking changes of planner data structures, so it will have to wait for a future major release.) option --with-zstd to enable Zstandard builds (Jeevan Ladhe, Robert Haas, Michael Paquier) • Add an ABI identifier field to the magic block in loadable libraries, allowing non-community Post- greSQL distributions

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI-breaking changes of planner data structures, so it will have to wait for a future major release.) option --with-zstd to enable Zstandard builds (Jeevan Ladhe, Robert Haas, Michael Paquier) • Add an ABI identifier field to the magic block in loadable libraries, allowing non-community Post- greSQL distributions

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI- breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI-breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI- breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI- breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI- breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI-breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI-breaking changes of planner data structures, so it will have to wait for a future major release.)

build the core server is not really recommended; in the worst case it could result in hard-to-debug ABI inconsistencies. You can also select a non-default sysroot path when configuring, by specifying PG_SYSROOT remote join, so disable generation of remote joins in such cases. (A better solution will require ABI-breaking changes of planner data structures, so it will have to wait for a future major release.)