aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.h
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-19 11:44:39 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-19 11:44:39 -0400
commit6991e774e0304f5ef488cf1ae4fa79578b6ae3d5 (patch)
treea2e0202f54a61f07eb1cd6173386dfedf8a04f34 /contrib/postgres_fdw/postgres_fdw.h
parent2731ce1bd550d08f3fdd7bcb1497af4b95170976 (diff)
downloadpostgresql-6991e774e0304f5ef488cf1ae4fa79578b6ae3d5.tar.gz
postgresql-6991e774e0304f5ef488cf1ae4fa79578b6ae3d5.zip
Provide feature-test macros for libpq features added in v14.
We had a request to provide a way to test at compile time for the availability of the new pipeline features. More generally, it seems like a good idea to provide a way to test via #ifdef for all new libpq API features. People have been using the version from pg_config.h for that; but that's more likely to represent the server version than the libpq version, in the increasingly-common scenario where they're different. It's safer if libpq-fe.h itself is the source of truth about what features it offers. Hence, establish a policy that starting in v14 we'll add a suitable feature-is-present macro to libpq-fe.h when we add new API there. (There doesn't seem to be much point in applying this policy retroactively, but it's not too late for v14.) Tom Lane and Alvaro Herrera, per suggestion from Boris Kolpackov. Discussion: https://postgr.es/m/boris.20210617102439@codesynthesis.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.h')
0 files changed, 0 insertions, 0 deletions