alternatives - Search results in mailing lists
Mailing lists >> pgsql-committers >> Thread
2025-05-22 18:23:36 | pgsql: pg_dump: Adjust reltuples from 0 to -1 for dumps of older versio (Nathan Bossart)
alternatively teach pg_restore_relation_stats() to translate reltuples based on the version argument, but since
Mailing lists >> pgsql-committers >> Thread
2025-04-20 13:13:15 | pgsql: Fix issue with ORDER BY / DISTINCT aggregates and FILTER (David Rowley)
alternative fix would have been to completely disallow the presorted optimization for Aggrefs with any FILTER
Mailing lists >> pgsql-committers >> Thread
2025-04-20 13:12:52 | pgsql: Fix issue with ORDER BY / DISTINCT aggregates and FILTER (David Rowley)
alternative fix would have been to completely disallow the presorted optimization for Aggrefs with any FILTER
Mailing lists >> pgsql-committers >> Thread
2025-04-20 13:12:27 | pgsql: Fix issue with ORDER BY / DISTINCT aggregates and FILTER (David Rowley)
alternative fix would have been to completely disallow the presorted optimization for Aggrefs with any FILTER
Mailing lists >> pgsql-committers >> Thread
2025-04-10 11:01:47 | pgsql: Fix data loss in logical replication. (Amit Kapila)
alternative approach considered was to take a strong lock on each affected table during publication
Mailing lists >> pgsql-committers >> Thread
2025-04-10 11:01:47 | pgsql: Fix data loss in logical replication. (Amit Kapila)
alternative approach considered was to take a strong lock on each affected table during publication
Mailing lists >> pgsql-committers >> Thread
2025-04-10 11:01:47 | pgsql: Fix data loss in logical replication. (Amit Kapila)
alternative approach considered was to take a strong lock on each affected table during publication
Mailing lists >> pgsql-committers >> Thread
2025-04-10 11:01:47 | pgsql: Fix data loss in logical replication. (Amit Kapila)
alternative approach considered was to take a strong lock on each affected table during publication
Mailing lists >> pgsql-committers >> Thread
2025-04-10 11:01:47 | pgsql: Fix data loss in logical replication. (Amit Kapila)
alternative approach considered was to take a strong lock on each affected table during publication
Mailing lists >> pgsql-committers >> Thread
2025-03-15 23:04:41 | pgsql: Optimization for lower(), upper(), casefold() functions. (Jeff Davis)
alternatives and settled on the
generated branches.
Author: Alexander Borisov
Mailing lists >> pgsql-committers >> Thread
2025-03-01 02:12:11 | pgsql: Re-export NextCopyFromRawFields() to copy.h. (Masahiko Sawada)
alternative, certain use cases still require NextCopyFromRawFields(). For instance, extensions like file_text_array_fdw, which
Mailing lists >> pgsql-committers >> Thread
2025-02-26 19:51:04 | Re: pgsql: Prepare for Python "Limited API" in PL/Python (Tom Lane)
alternative_names_49201 (s= )) at /usr/src/debug/python3-3.6.8-69.el8_10.x86_64/Python/ceval.c:752 #8 _PyFunction_FastCall (globals= , nargs= , args= , co= ) at /usr/src/debug/python3-3.6.8-69.el8_10.x86_64/Python/ceval.c
Mailing lists >> pgsql-committers >> Thread
2025-02-21 11:14:17 | pgsql: Drop opcintype from index AM strategy translation API (Peter Eisentraut)
alternative of using InvalidOid as argument(s) upsets various DDL commands, so it's not practical
Mailing lists >> pgsql-committers >> Thread
2025-02-11 00:31:34 | pgsql: Adapt appendPsqlMetaConnect() to the new fmtId() encoding expect (Tom Lane)
alternative of having pg_upgrade use setFmtEncoding() is unappetizing, given that it's connecting to multiple
Mailing lists >> pgsql-committers >> Thread
2025-02-11 00:31:34 | pgsql: Adapt appendPsqlMetaConnect() to the new fmtId() encoding expect (Tom Lane)
alternative of having pg_upgrade use setFmtEncoding() is unappetizing, given that it's connecting to multiple