| Replied (own) | TAP tests aren't using the magic words for Windows file access | almost 7 years ago |
| Replied (other) | Precision/scale of a numeric attribute of a new data type are not handled correctly when the type is returned by a function | almost 7 years ago |
| Started thread | pgsql: Doc: improve discussion of race conditions involved in LISTEN. | almost 7 years ago |
| Replied (other) | Assertion failing in master, predicate.c | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Avoid assertion failure with LISTEN in a serializable transactio | almost 7 years ago |
| Started thread | pgsql: Stabilize NOTIFY behavior by transmitting notifies before ReadyF | almost 7 years ago |
| Started thread | pgsql: Stabilize NOTIFY behavior by transmitting notifies before ReadyF | almost 7 years ago |
| Started thread | pgsql: Stabilize NOTIFY behavior by transmitting notifies before ReadyF | almost 7 years ago |
| Started thread | pgsql: Stabilize NOTIFY behavior by transmitting notifies before ReadyF | almost 7 years ago |
| Started thread | pgsql: Stabilize NOTIFY behavior by transmitting notifies before ReadyF | almost 7 years ago |
| Started thread | pgsql: Stabilize the results of pg_notification_queue_usage(). | almost 7 years ago |
| Replied (own) | LISTEN/NOTIFY testing woes | almost 7 years ago |
| Replied (own) | LISTEN/NOTIFY testing woes | almost 7 years ago |
| Replied (other) | BUG #16134: Assertion fails on CREATE gist INDEX over intarray | almost 7 years ago |
| Replied (other) | [PATCH] Style, remove redudant test "if (zeropadlen > 0)" | almost 7 years ago |
| Started thread | pgsql: Remove a couple of unnecessary if-tests. | almost 7 years ago |
| Replied (other) | [PATCH] Possible arithmetic with NULL pointer or test "stack_base_ptr != NULL" is irrelevant. | almost 7 years ago |
| Replied (other) | here does postgres take its timezone information from? | almost 7 years ago |
| Replied (own) | LISTEN/NOTIFY testing woes | almost 7 years ago |
| Replied (other) | Copyright information in source files | almost 7 years ago |
| Started threadFirst patch | LISTEN/NOTIFY testing woes | almost 7 years ago |
| Started thread | pgsql: Improve test coverage for LISTEN/NOTIFY. | almost 7 years ago |
| Started thread | pgsql: Improve test coverage for LISTEN/NOTIFY. | almost 7 years ago |
| Started thread | pgsql: Improve test coverage for LISTEN/NOTIFY. | almost 7 years ago |
| Started thread | pgsql: Improve test coverage for LISTEN/NOTIFY. | almost 7 years ago |
| Replied (other) | Trouble incrementing a column | almost 7 years ago |
| Replied (other) | Remote Connection Help | almost 7 years ago |
| Replied (other) | Constants in the foreighn key constraints | almost 7 years ago |
| Replied (own) | XID-wraparound hazards in LISTEN/NOTIFY | almost 7 years ago |
| Started thread | XID-wraparound hazards in LISTEN/NOTIFY | almost 7 years ago |
| Replied (other) | errbacktrace | almost 7 years ago |
| Replied (other) | Assertion failing in master, predicate.c | almost 7 years ago |
| Replied (other) | Assertion failing in master, predicate.c | almost 7 years ago |
| Replied (other) | [PATCH] Tiny optmization. | almost 7 years ago |
| Replied (own) | Getting psql to redisplay command after \e | almost 7 years ago |
| Started thread | pgsql: Make psql redisplay the query buffer after \e. | almost 7 years ago |
| Replied (own) | TAP tests aren't using the magic words for Windows file access | almost 7 years ago |
| Replied (other) | BUG #16133: Regexp quantifier issues | almost 7 years ago |
| Replied (other) | Why overhead of SPI is so large? | almost 7 years ago |
| Started thread | pgsql: Avoid taking a new snapshot for an immutable simple expression i | almost 7 years ago |
| Replied (other) | Assertion failing in master, predicate.c | almost 7 years ago |
| Started thread | pgsql: Add test coverage for "unchanged toast column" replication code | almost 7 years ago |
| Started thread | pgsql: Add test coverage for "unchanged toast column" replication code | almost 7 years ago |
| Started thread | pgsql: Add test coverage for "unchanged toast column" replication code | almost 7 years ago |
| Started thread | pgsql: Add test coverage for "unchanged toast column" replication code | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Started thread | pgsql: Fix bogus tuple-slot management in logical replication UPDATE ha | almost 7 years ago |
| Started thread | pgsql: Fix bogus tuple-slot management in logical replication UPDATE ha | almost 7 years ago |
| Started thread | pgsql: Fix bogus tuple-slot management in logical replication UPDATE ha | almost 7 years ago |
| Started thread | pgsql: Fix bogus tuple-slot management in logical replication UPDATE ha | almost 7 years ago |
| Replied (other) | Ordering of header file inclusion | almost 7 years ago |
| Replied (other) | Assertion failing in master, predicate.c | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Replied (other) | obsolete example | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Replied (other)First patch | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Replied (other) | BUG #16129: Segfault in tts_virtual_materialize in logical replication worker | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Started thread | pgsql: Defend against self-referential views in relation_is_updatable() | almost 7 years ago |
| Replied (other) | Copyright information in source files | almost 7 years ago |
| Replied (other) | Remote Connection Help | almost 7 years ago |
| Replied (other) | Remote Connection Help | almost 7 years ago |
| Replied (other) | Why overhead of SPI is so large? | almost 7 years ago |
| Replied (other) | Remote Connection Help | almost 7 years ago |
| Replied (other) | Remote Connection Help | almost 7 years ago |
| Replied (other) | BUG #16130: planner does not pick unique btree index and goes for seq scan but unsafe hash index works. | almost 7 years ago |
| Replied (other) | an OID >= 8000 in master | almost 7 years ago |
| Replied (other) | an OID >= 8000 in master | almost 7 years ago |
| Replied (other) | BufFileRead() error signalling | almost 7 years ago |
| Replied (own) | CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? | almost 7 years ago |
| Replied (other) | Why overhead of SPI is so large? | almost 7 years ago |
| Started thread | pgsql: Sync patternsel_common's operator selection logic with pattern_p | almost 7 years ago |
| Started thread | pgsql: Reduce match_pattern_prefix()'s dependencies on index opfamilies | almost 7 years ago |
| Replied (other) | ALTER TABLE fails when changing column type due to index with bit_ops opclass | almost 7 years ago |
| Replied (other) | why doesn't optimizer can pull up where a > ( ... ) | almost 7 years ago |
| Replied (other) | Role membership and DROP | almost 7 years ago |
| Started thread | pgsql: Doc: improve discussion of object owners' inherent privileges. | almost 7 years ago |
| Replied (other) | why doesn't optimizer can pull up where a > ( ... ) | almost 7 years ago |
| Replied (other) | BUG #16127: PostgreSQL 12.1 on Windows 2008 R2 copy table from ‘large 2GB csv’report “Unknown error” | almost 7 years ago |
| Replied (other) | could not stat promote trigger file leads to shutdown | almost 7 years ago |
| Replied (other) | GSoD - a patch for Getting Started tutorial | almost 7 years ago |
| Replied (other)First patch | No = operator for opfamily 426 | almost 7 years ago |
| Started thread | pgsql: Fix corner-case failure in match_pattern_prefix(). | almost 7 years ago |
| Started thread | pgsql: Fix corner-case failure in match_pattern_prefix(). | almost 7 years ago |
| Replied (other) | documentation for WITH RECURSIVE | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify use of RECURSIVE in WITH. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Started thread | pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA. | almost 7 years ago |
| Replied (other)Follow-up patch | Role membership and DROP | almost 7 years ago |
| Replied (other) | BUG #16119: pg_dump omits columns specification for matviews | almost 7 years ago |
| Replied (other) | initdb SegFault | almost 7 years ago |
| Replied (other) | GSoD - a patch for Getting Started tutorial | almost 7 years ago |
| Replied (other) | No = operator for opfamily 426 | almost 7 years ago |
| Replied (other) | initdb SegFault | almost 7 years ago |
| Replied (other) | Postgres on IBM z/OS 2.2.0 and 2.3.0 | almost 7 years ago |
| Replied (other) | Invisible PROMPT2 | almost 7 years ago |
| Replied (other) | Reverse collations (initially for making keyset pagination cover more cases) | almost 7 years ago |
| Replied (other) | documentation for WITH RECURSIVE | almost 7 years ago |
| Replied (other) | Invisible PROMPT2 | almost 7 years ago |
| Replied (other) | BUG #16121: 12 regression: Volatile function in target list subquery behave as stable | almost 7 years ago |
| Replied (other) | BUG #16124: Altering default privileges problem | almost 7 years ago |
| Replied (other) | BUG #16123: DST not respected for America/Sao_Paulo in `timestamp` function | almost 7 years ago |
| Replied (other) | here does postgres take its timezone information from? | almost 7 years ago |