| Replied (other) | BUG #16555: Postgresql is not LTO ready | almost 6 years ago |
| Replied (other) | [PATCH] Performance Improvement For Copy From Binary Files | almost 6 years ago |
| Replied (own) | Mark unconditionally-safe implicit coercions as leakproof | almost 6 years ago |
| Replied (other) | INSERT INTO SELECT, Why Parallelism is not selected? | almost 6 years ago |
| Replied (other) | UTF8 conversion | almost 6 years ago |
| Replied (other) | bad JIT decision | almost 6 years ago |
| Replied (other) | BUG #16554: Consistent sequence gaps occuring next day | almost 6 years ago |
| Replied (other) | subquery column error causes data destroying equality | almost 6 years ago |
| Replied (other) | bad JIT decision | almost 6 years ago |
| Replied (other) | bad JIT decision | almost 6 years ago |
| Replied (other) | bad JIT decision | almost 6 years ago |
| Replied (other)First patch | Row estimates for empty tables | almost 6 years ago |
| Replied (other) | when is RLS policy applied | almost 6 years ago |
| Replied (other) | Row estimates for empty tables | almost 6 years ago |
| Replied (other) | when is RLS policy applied | almost 6 years ago |
| Replied (other) | [PATCH] fix GIN index search sometimes losing results | almost 6 years ago |
| Replied (other) | Missing CFI in hlCover()? | almost 6 years ago |
| Replied (other) | Missing CFI in hlCover()? | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (other) | Missing CFI in hlCover()? | almost 6 years ago |
| Started threadFirst patch | Mark unconditionally-safe implicit coercions as leakproof | almost 6 years ago |
| Replied (own)Follow-up patch | Making CASE error handling less surprising | almost 6 years ago |
| Replied (other) | INSERT INTO SELECT, Why Parallelism is not selected? | almost 6 years ago |
| Replied (other) | Row estimates for empty tables | almost 6 years ago |
| Replied (other) | renaming configure.in to configure.ac | almost 6 years ago |
| Replied (own)Follow-up patch | Making CASE error handling less surprising | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (own) | Making CASE error handling less surprising | almost 6 years ago |
| Replied (other) | BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data | almost 6 years ago |
| Replied (other) | 'with' regression tests fails rarely (and spuriously) | almost 6 years ago |
| Started threadFirst patch | Making CASE error handling less surprising | almost 6 years ago |
| Replied (other) | BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE | almost 6 years ago |
| Replied (other) | Building 12.3 from source on Mac | almost 6 years ago |
| Replied (other) | Building 12.3 from source on Mac | almost 6 years ago |
| Replied (other) | Building 12.3 from source on Mac | almost 6 years ago |
| Replied (other) | expose parallel leader in CSV and log_line_prefix | almost 6 years ago |
| Replied (other) | psql \r changed behavior in pg10 | almost 6 years ago |
| Replied (other) | Why it is not possible to create custom AM which behaves similar to btree? | almost 6 years ago |
| Replied (own) | Infinities in type numeric | almost 6 years ago |
| Replied (other) | BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data | almost 6 years ago |
| Replied (other) | BUG #16549: "CASE" not work properly , the function works properly on PostgreSQL 9.6.8 | almost 6 years ago |
| Replied (other) | [PATCH] fix GIN index search sometimes losing results | almost 6 years ago |
| Replied (other) | BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data | almost 6 years ago |
| Replied (other) | v13 planner ERROR: could not determine which collation to use for string comparison | almost 6 years ago |
| Replied (other) | v13 planner ERROR: could not determine which collation to use for string comparison | almost 6 years ago |
| Replied (own)Follow-up patch | Infinities in type numeric | almost 6 years ago |
| Replied (other) | xl_heap_header alignment? | almost 6 years ago |
| Replied (own) | pg_subscription.subslotname is wrongly marked NOT NULL | almost 6 years ago |
| Replied (other) | Improving psql slash usage help message | almost 6 years ago |
| Replied (other) | BUG #16548: Order by on array element giving disparity in result | almost 6 years ago |
| Replied (other) | Logical replication from 11.x to 12.x and "unique key violations" | almost 6 years ago |
| Replied (own) | Wrong results from in_range() tests with infinite offset | almost 6 years ago |
| Replied (own) | NaN divided by zero should yield NaN | almost 6 years ago |
| Replied (own)Follow-up patch | pg_subscription.subslotname is wrongly marked NOT NULL | almost 6 years ago |
| Replied (other) | Binary support for pgoutput plugin | almost 6 years ago |
| Replied (other) | Logical replication from 11.x to 12.x and "unique key violations" | almost 6 years ago |
| Replied (other) | Improvement for query planner? (no, not about count(*) again ;-)) | almost 6 years ago |
| Replied (other) | Logical replication from 11.x to 12.x and "unique key violations" | almost 6 years ago |
| Replied (other) | Binary support for pgoutput plugin | almost 6 years ago |
| Replied (other) | PGBench on Windows - connections are subprocesses? | almost 6 years ago |
| Replied (other) | Default setting for enable_hashagg_disk | almost 6 years ago |