alternatives - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 19:37:40 | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) (Andres Freund)
Alternatively we could try deferring more of openssl's initialization to outside of postmaster - but that
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 15:09:21 | Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait (Xuneng Zhou)
alternative approach would be to adopt a hybrid strategy: - For logical replication use cases: Apply
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 10:00:05 | Proposal: Global Index for PostgreSQL (Dilip Kumar)
alternative strategy, we could allocate a new partition ID and just leave the index entries
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 08:03:07 | Re: What's our minimum supported Python version? (Peter Eisentraut)
Python 3.6, we can also remove PL/Python test alternative expected files for earlier Python versions. See attached patch.
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (4)
2025-06-05 18:21:20 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly (Vitaly Davydov)
alternative solution. I think, we can update xmin horizon in checkpoint only but the horizon
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-06-05 10:03:49 | Re: ZStandard (with dictionaries) compression support for TOAST compression (Nikhil Kumar Veldanda)
Alternatively, one could use: #define READ_U32_UNALIGNED(src) \ ({ \ uint32 _tmp; \ memcpy(&_tmp, (src), sizeof
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 13:40:07 | Re: pull-up subquery if JOIN-ON contains refs to upper-query (Alena Rybakina)
alternative plan but I'm still learning this. For example: create table t(x int); create
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 10:06:58 | pg_probackup build issue with PostgreSQL 18beta1 due to pg_detoast_datum_packed() (Japin Li)
like pg_probackup. Any thoughts or alternative suggestions would be greatly appreciated! -- Regards, Japin Li
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 09:15:12 | Re: C11 / VS 2019 (Peter Eisentraut)
alternative approach would be to turn on C11 and add another option to explicitly turn
Mailing lists >> pgsql-hackers >> Thread
2025-05-29 21:24:03 | Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them (Matthias van de Meent)
alternative data sources, or e.g. calling a user-defined SECURITY INVOKER function. PG18 still seems
Mailing lists >> pgsql-hackers >> Thread
2025-05-29 00:59:35 | Re: pg16 && GSSAPI && Heimdal/Macos (Tom Lane)
alternative implementation was void pg_store_delegated_credential(gss_cred_id_t cred) { #ifdef HAVE
Mailing lists >> pgsql-hackers >> Thread
2025-05-27 21:38:19 | Tightening DecodeNumberField's parsing rules (Tom Lane)
alternatively apply some more-limited fix; Evgeniy's original recommendation was just to reject if the result
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (5)
2025-05-26 22:36:14 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
alternatively define that case as a no-op, but that seems too + * likely to mask
Mailing lists >> pgsql-hackers >> Thread
2025-05-21 21:40:28 | Re: [PATCH] avoid double scanning in function byteain (Peter Eisentraut)
alternatives? The description doesn't make this clear. Some of the changes in patch 0002 just
Mailing lists >> pgsql-hackers >> Thread
2025-05-21 00:23:11 | Re: Assert("vacrel->eager_scan_remaining_successes > 0") (Masahiko Sawada)
Alternatively, if the excess scanning proves negligible in practice, we could adopt a simpler solution