| Replied (own)First patch | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (own) | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | missing warning in pg_import_system_collations | almost 5 years ago |
| Replied (own) | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | How to observe plan_cache_mode transition from custom to generic plan? | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor | almost 5 years ago |
| Replied (other) | How to observe plan_cache_mode transition from custom to generic plan? | almost 5 years ago |
| Replied (other) | BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Replied (other) | missing warning in pg_import_system_collations | almost 5 years ago |
| Replied (other) | trap instead of error on 32 TiB table | almost 5 years ago |
| Replied (other) | trap instead of error on 32 TiB table | almost 5 years ago |
| Replied (other) | Regression in PG14 LookupFuncName | almost 5 years ago |