diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2017-08-03 14:48:54 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2017-08-03 14:54:28 -0400 |
| commit | 9a3b5d3ad0f1c19c47e2ee65b372344cb0616c9a (patch) | |
| tree | 8a04d305bec58c6ffc2ddab1ddc5d9db938bd66e /src/backend/commands/explain.c | |
| parent | 972b6ec20bf090a18145624f8092d2cb1715ab83 (diff) | |
| download | postgresql-9a3b5d3ad0f1c19c47e2ee65b372344cb0616c9a.tar.gz postgresql-9a3b5d3ad0f1c19c47e2ee65b372344cb0616c9a.zip | |
Fix build on zlib-less environments
Commit 4d57e8381677 added support for getting I/O errors out of zlib,
but it introduced a portability problem for systems without zlib.
Repair by wrapping the zlib call inside #ifdef and restore the original
code in the other branch.
This serves to illustrate the inadequacy of the zlib abstraction in
pg_backup_archiver: there is no way to call gzerror() in that
abstraction. This means that the several places that call GZREAD and
GZWRITE are currently doing error reporting wrongly, but ENOTIME to get
it fixed before next week's release set.
Backpatch to 9.4, like the commit that introduced the problem.
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions