Debian Patches
Status for postgresql-17/17.3-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 50-per-version-dirs.patch | Use version specific installation directories so that several major versions can be installed in parallel. * Install lib files into /usr/lib/postgresql/<version>/lib/ * Install server related header files into /usr/include/postgresql/<version>/server/ |
Martin Pitt <mpitt@debian.org> | invalid | debian | ||
| 51-default-sockets-in-var.patch | Put server Unix sockets into /var/run/postgresql/ by default Using /tmp for sockets allows everyone to spoof a PostgreSQL server. Thus use /var/run/postgresql/ for "system" clusters which run as 'postgres' (user clusters will still use /tmp). Since system cluster are by far the common case, set it as default. |
Martin Pitt <mpitt@debian.org> | invalid | |||
| 52-tutorial-README.patch | Update tutorial README for required build dependencies. | Martin Pitt <mpitt@debian.org> | invalid | |||
| 53-pg_service.conf_directory_doc.patch | Update pg_service.conf example to tell the Debian specific file location. =================================================================== |
Martin Pitt <mpitt@debian.org> | invalid | |||
| 54-debian-alternatives-for-external-tools.patch | Use Debian alternatives for external tools instead of hardcoded programs | Martin Pitt <mpitt@debian.org> | invalid | |||
| 70-history | Document Debian location of release notes files. | Christoph Berg <myon@debian.org> | invalid | |||
| filter-debug-prefix-map | To make the PostgreSQL server packages build reproducibly, we need to remove the build path from -fdebug-prefix-map and -ffile-prefix-map in CFLAGS. * The actual server build still uses the original CFLAGS so the build path is correctly mapped in the object files. * The information printed by the pg_config binary and the system view is filtered in src/common/Makefile and the configure script. * The build paths stored in Makefile.global are filtered in debian/rules. (abs_top_builddir, abs_top_srcdir, configure_args, CFLAGS) * To make PGXS module builds reproducible, pg_buildext copies the environment CFLAGS to COPT where Makefile.global picks them up, using the prefix maps from dpkg-buildflags. |
no | ||||
| libpgport-pkglibdir | Move libpgport/libpgcommon/libpgfeutils from libdir to pkglibdir This allows client applications to link to version-specific libraries. Used by pg-checksums. |
Christoph Berg <myon@debian.org> | invalid | |||
| extension_destdir | no | |||||
| autoconf2.69 | no | |||||
| focal-arm64-outline-atomics | Enable outline-atomics on arm64. The flag was added in focal's gcc, but is off by default there. It is enabled by default on all later distributions (hirsute, impish, bullseye, bookwork, sid). https://www.postgresql.org/message-id/flat/1635221042457.21654%40amazon.com This patch can be removed once focal is EOL. |
no | ||||
| jit-s390x | [PATCH] jit: Workaround potential datalayout mismatch on s390x LLVM's s390x target uses a different datalayout for z13 and newer processors. If llvmjit_types.bc is compiled to target a processor older than z13, and then the JIT runs on a z13 or newer processor, then there will be a mismatch in datalayouts between llvmjit_types.bc and the JIT engine. This mismatch causes the JIT to fail at runtime. |
Tom Stellard <tstellar@redhat.com> | no | 2021-04-20 | ||
| hurd-iovec | hurd-i386 does not define IOV_MAX | no | ||||
| pgstat-report-conflicts-immediately.patch | diff --git i/src/backend/utils/activity/pgstat_database.c w/src/backend/utils/activity/pgstat_database.c index 7149f22f729..bb36d73ec04 100644 |
no | ||||
| efdadeb2238f5b5f0f32df2f3e7d277d1faf1c4f | commit efdadeb2238f5b5f0f32df2f3e7d277d1faf1c4f Fix PQescapeLiteral()/PQescapeIdentifier() length handling In 5dc1e42b4fa I fixed bugs in various escape functions, unfortunately as part of that I introduced a new bug in PQescapeLiteral()/PQescapeIdentifier(). The bug is that I made PQescapeInternal() just use strlen(), rather than taking the specified input length into account. That's bad, because it can lead to including input that wasn't intended to be included (in case len is shorter than null termination of the string) and because it can lead to reading invalid memory if the input string is not null terminated. Expand test_escape to this kind of bug: a) for escape functions with length support, append data that should not be escaped and check that it is not b) add valgrind requests to detect access of bytes that should not be touched Author: Tom Lane <tgl@sss.pgh.pa.us> Author: Andres Freund <andres@anarazel.de Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Noah Misch <noah@leadboat.com> Discussion: https://postgr.es/m/Z64jD3u46gObCo1p@pryzbyj2023 Backpatch: 13 diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c index e97ad025427..120d4d032ec 100644 |
Andres Freund <andres@anarazel.de> | no | 2025-02-14 |
All known versions for source package 'postgresql-17'
- 17.3-3 (sid, trixie)