| Replied (own) | StandbyRecoverPreparedTransactions recovers subtrans links incorrectly | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Started thread | pgsql: Fix order of arguments to SubTransSetParent(). | about 9 years ago |
| Replied (own) | StandbyRecoverPreparedTransactions recovers subtrans links incorrectly | about 9 years ago |
| Replied (own) | A note about debugging TAP failures | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Started thread | StandbyRecoverPreparedTransactions recovers subtrans links incorrectly | about 9 years ago |
| Started thread | pgsql: Make PostgresNode.pm check server status more carefully. | about 9 years ago |
| Started thread | pgsql: Make PostgresNode.pm check server status more carefully. | about 9 years ago |
| Replied (own) | A note about debugging TAP failures | about 9 years ago |
| Started thread | pgsql: Make PostgresNode::append_conf append a newline automatically. | about 9 years ago |
| Started thread | pgsql: Make PostgresNode::append_conf append a newline automatically. | about 9 years ago |
| Replied (own) | A note about debugging TAP failures | about 9 years ago |
| Started thread | PostgresNode::append_conf considered dangerous | about 9 years ago |
| Replied (other)Follow-up patch | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Started thread | A note about debugging TAP failures | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Started thread | pgsql: Partially revert commit 536d47bd9d5fce8d91929bee3128fa1d08dbcc57 | about 9 years ago |
| Replied (own)Follow-up patch | Unportable implementation of background worker start | about 9 years ago |
| Replied (own)Follow-up patch | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | pgsql: Replication lag tracking for walsenders | about 9 years ago |
| Replied (other) | Old versions of Test::More | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Started thread | pgsql: Avoid depending on non-POSIX behavior of fcntl(2). | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Started thread | pgsql: Remove long-obsolete catering for platforms without F_SETFD/FD_C | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own)Follow-up patch | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | intagg.sgml: example wrongly named and does not compile | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | Old versions of Test::More | about 9 years ago |
| Replied (other) | Incorrect type in pg_cast causes Postmaster to core dump | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own)First patch | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | why isn't this subquery wrong? | about 9 years ago |
| Replied (other) | WITH clause in CREATE STATISTICS | about 9 years ago |
| Replied (other) | Removing select(2) based latch (was Unportable implementation of background worker start) | about 9 years ago |
| Replied (other) | Removing select(2) based latch (was Unportable implementation of background worker start) | about 9 years ago |
| Replied (other) | Use sync commit for logical replication apply in TAP tests | about 9 years ago |
| Replied (other) | Removing select(2) based latch (was Unportable implementation of background worker start) | about 9 years ago |
| Replied (own) | OK, so culicidae is *still* broken | about 9 years ago |
| Started thread | pgsql: Add missing erand48.c to libpq/.gitignore. | about 9 years ago |
| Started thread | pgsql: Sync pg_ctl documentation and usage message with reality. | about 9 years ago |
| Replied (other) | WIP Patch: Precalculate stable functions | about 9 years ago |
| Replied (other) | BUG #14628: regex description in online documentation misleadingly/wrong | about 9 years ago |
| Replied (other) | Partition-wise join for join between (declaratively) partitioned tables | about 9 years ago |
| Replied (other) | referential integrity between elements of an array and another table? | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | BUG #14627: fail initdb | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (own) | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | pg_dump(1) failures when concurrently refreshing mat views | about 9 years ago |
| Started thread | Unportable implementation of background worker start | about 9 years ago |
| Replied (other) | pg_dump(1) failures when concurrently refreshing mat views | about 9 years ago |
| Replied (other) | BUG #14626: array_agg( anyarray ) unexpected error with multi-valued single-dimension array | about 9 years ago |
| Replied (other) | Highly Variable Planning Times | about 9 years ago |
| Replied (other) | BuildFarm client release 4.19 | about 9 years ago |
| Started thread | Cost of src/test/recovery and .../subscription tests | about 9 years ago |
| Replied (other) | tuple statistics update | about 9 years ago |
| Replied (own) | OK, so culicidae is *still* broken | about 9 years ago |
| Replied (own) | Inadequate parallel-safety check for SubPlans | about 9 years ago |
| Replied (other) | Should pg_current_wal_location() become pg_current_wal_lsn() | about 9 years ago |
| Replied (other) | tuple statistics update | about 9 years ago |
| Replied (own) | Inadequate parallel-safety check for SubPlans | about 9 years ago |
| Started thread | pgsql: Fix testing of parallel-safety of SubPlans. | about 9 years ago |
| Started thread | pgsql: Doc: improve markup in self-signed certificate example. | about 9 years ago |
| Replied (other) | Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f) | about 9 years ago |
| Started thread | pgsql: Provide an error cursor for "can't call an SRF here" errors. | about 9 years ago |
| Replied (own) | Why does logical replication launcher set application_name? | about 9 years ago |
| Replied (own) | Why does logical replication launcher set application_name? | about 9 years ago |
| Replied (other) | Continuous buildfarm failures on hamster with bin-check | about 9 years ago |
| Replied (other) | Continuous buildfarm failures on hamster with bin-check | about 9 years ago |
| Replied (other)First patch | Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f) | about 9 years ago |
| Replied (other) | Self-signed certificate instructions | about 9 years ago |
| Replied (other) | Possible problem in Custom Scan API | about 9 years ago |
| Started thread | pgsql: Always build a custom plan node's targetlist from the path's pat | about 9 years ago |
| Started thread | pgsql: Always build a custom plan node's targetlist from the path's pat | about 9 years ago |
| Started thread | pgsql: Always build a custom plan node's targetlist from the path's pat | about 9 years ago |
| Started thread | pgsql: Support OpenSSL 1.1.0 in 9.3 and 9.2. | about 9 years ago |
| Started thread | pgsql: Support OpenSSL 1.1.0 in 9.3 and 9.2. | about 9 years ago |
| Replied (own) | Cutting initdb's runtime (Perl question embedded) | about 9 years ago |
| Replied (own) | Cutting initdb's runtime (Perl question embedded) | about 9 years ago |
| Replied (own) | pgsql: Fix integer-overflow problems in interval comparison. | about 9 years ago |
| Started thread | pgsql: Back-patch 9.4-era SSL renegotiation code into 9.3 and 9.2. | about 9 years ago |
| Started thread | pgsql: Back-patch 9.4-era SSL renegotiation code into 9.3 and 9.2. | about 9 years ago |
| Replied (own) | Inadequate parallel-safety check for SubPlans | about 9 years ago |
| Replied (other) | How to add columns to view with dependencies | about 9 years ago |
| Started thread | pgsql: Ensure BackgroundWorker struct contents are well-defined. | about 9 years ago |