pq-sys

What's Changed

• Reinclude wrapper.h by @weiznich in #95

Full Changelog: v0.7.4...v0.7.5

What's Changed

• Exclude generate_bindings.sh script from published package by @weiznich in #94

Full Changelog: v0.7.3...v0.7.4

• Update the bundled version of libpq to 18.0
• Regenerate bindings for the new postgres release
• Enable the pkg-config feature by default

Full Changelog: v0.7.2...v0.7.3

What's Changed

• Bump bindgen to 0.72.0 and regenerate bindings
• Fixed an issue with bundled builds without openssl on windows due to a breaking upstream rust change

Full Changelog: v0.3.8...v0.7.2

• Restore compatibilities with non-cargo build systems
• Add a safe-guard to make sure users get a better error message if the build script is not run

Changed

• pq-src starting with version 0.3 now depends on openssl on windows as well add support for the scram-sha-256 authentication method
• pq-sys adds support for pq-src 0.3.0

Changed

• The bundled feature of pq-sys no longer build a bundled version of openssl. To bundle openssl when compiling libpq from source, add openssl-sys with the vendored feature to your crate dependencies:

  [dependencies]
  openssl-sys = { version = "0.9.93", features = ["vendored"] }
  

Added

• We added a pq-src crate and a bundled feature for pq-sys. This allows to build and link a static version of libpq during the rust build process. This feature currently supports builds targeting Windows, Linux and macOS. It requires a c-compiler toolchain for the target to build libpq from source.
• We added a buildtime_bindgen feature flag that allows to generate bindings for your locally installed libpq version. This is helpful for cases where the target architecture is significantly different to what the built-in bindings assume.

Changed

• We regenerated the bundled bindings to match the libpq version build by the bundled feature flag

Added

• Linking can now be dynamically handled per-target by specifying the TARGET environment variable and PQ_LIB_STATIC_$TARGET environment variable.

• The path to pg_config can now be dynamically handled per-target by specifying the TARGET environment variable and PG_CONFIG_$TARGET environment variable.

Fixed

• Linking on the msvc toolchain will no longer attempt to statically link

Fixed

• Improved linking on Windows, particularly with the msvc toolchain.

Fixed

• Properly specified the build script

Changed

• Bindings are no longer generated at compile time. Requiring clang 3.9 caused too many issues for too many users, and requiring syntex_syntax increased compile time too much.

Fixed

• Fixed an issue when building on mac against postgres from homebrew

Fixed

• Fixed an issue when building on mac against postgres from homebrew

• Fixed an issue with locating header files on linux

Changed

• Bindings are now generated when the library is built, rather than being vendored ahead of time.

• libc is no longer used. Anywhere that libc::some_type was expected, std::os::raw::some_type is now used instead.

• The build script will no longer attempt to canonicalize symlinks on MacOS.

Changed

• pkg-config is disabled by default. It can be enabled by adding features = ["pkg-config"] to your Cargo.toml.

Added

• We will attempt to use pkg-config to locate libpq before falling back to pg_config.

• No changes. Accidental release on the wrong commit.

Added

• pq will be statically linked if the environment variable PQ_LIB_STATIC is set.

Changed

• On Mac if pg_config points to a directory where libpq.dylib is a symlink, we will now attempt to find the canonical directory to link against. This means that for installations using homebrew, /usr/local/Cellar/postgresql/version/lib will be added to DYLD_LIBRARY_PATH instead of /usr/local/lib

Added

• The directory containing libpq for linking can now be specified via the PQ_LIB_DIR environment variable.

Changed

• We updated the bundled libpq version to 16.2 to fix compatibility with openssl 3.2
• We changed the build script to expose the bundled libpq headers by setting DEP_PQ_SYS_SRC_INCLUDE so that other *-sys crates can consume that information and reuse the bundled build provided by this crate