| Replied (own) | Oddity in EXPLAIN for foreign/custom join pushdown plans | about 10 years ago |
| Replied (own) | Oddity in EXPLAIN for foreign/custom join pushdown plans | about 10 years ago |
| Replied (own) | Oddity in EXPLAIN for foreign/custom join pushdown plans | about 10 years ago |
| Replied (own) | Oddity in EXPLAIN for foreign/custom join pushdown plans | about 10 years ago |
| Started threadFirst patch | Oddity in EXPLAIN for foreign/custom join pushdown plans | about 10 years ago |
| Replied (own)Follow-up patch | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Replied (own) | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Replied (own)Follow-up patch | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Replied (own) | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Replied (own) | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Started threadFirst patch | Oddity in handling of cached plans for FDW queries | about 10 years ago |
| Replied (own) | doc: Incorrect return type of IsForeignScanParallelSafe in fdwhandler.sgml | about 10 years ago |
| Started threadFirst patch | doc: Incorrect return type of IsForeignScanParallelSafe in fdwhandler.sgml | about 10 years ago |
| Replied (other) | Postgres_fdw join pushdown - wrong results with whole-row reference | about 10 years ago |
| Replied (own)Follow-up patch | Odd system-column handling in postgres_fdw join pushdown patch | about 10 years ago |