| Replied (other) | Reset snapshot export state on the transaction abort | almost 5 years ago |
| Replied (own)First patch | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Replied (other) | Reset snapshot export state on the transaction abort | almost 5 years ago |
| Replied (other) | Trivial doc patch | almost 5 years ago |
| Replied (other) | Re: Inconsistent behavior of pg_dump/pg_restore on DEFAULT PRIVILEGES | almost 5 years ago |
| Replied (other) | Reset snapshot export state on the transaction abort | almost 5 years ago |
| Replied (own) | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Replied (own) | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Replied (other) | BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable | almost 5 years ago |
| Replied (other) | should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function? | almost 5 years ago |
| Started thread | pgsql: Fix use-after-free with multirange types in CREATE TYPE | almost 5 years ago |
| Started thread | pgsql: Fix use-after-free with multirange types in CREATE TYPE | almost 5 years ago |
| Replied (other) | Reset snapshot export state on the transaction abort | almost 5 years ago |
| Replied (other) | Bug in DefineRange() with multiranges | almost 5 years ago |
| Replied (other) | BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable | almost 5 years ago |
| Replied (other) | BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 | almost 5 years ago |
| Replied (other) | should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function? | almost 5 years ago |
| Started thread | pgsql: Fix tests of pg_upgrade across different major versions | almost 5 years ago |
| Started thread | pgsql: Fix tests of pg_upgrade across different major versions | almost 5 years ago |
| Started thread | pgsql: Fix tests of pg_upgrade across different major versions | almost 5 years ago |
| Started thread | pgsql: Fix tests of pg_upgrade across different major versions | almost 5 years ago |
| Replied (own) | Rewriting the test of pg_upgrade as a TAP test - take three - remastered set | almost 5 years ago |
| Replied (own) | Rewriting the test of pg_upgrade as a TAP test - take three - remastered set | almost 5 years ago |
| Replied (own) | More business with $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Started thread | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Started thread | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Started thread | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Started thread | pgsql: Add more $Test::Builder::Level in the TAP tests | almost 5 years ago |
| Replied (other) | VS2022: Support Visual Studio 2022 on Windows | almost 5 years ago |
| Replied (other)Follow-up patch | BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 | almost 5 years ago |
| Replied (other) | Parallel vacuum workers prevent the oldest xmin from advancing | almost 5 years ago |
| Replied (other) | strange case of "if ((a & b))" | almost 5 years ago |
| Started thread | pgsql: Clean up more code using "(expr) ? true : false" | almost 5 years ago |
| Replied (own) | Rewriting the test of pg_upgrade as a TAP test - take three - remastered set | almost 5 years ago |