| Replied (other) | Performance regression with PostgreSQL 11 and partitioning | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (other) | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (other) | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (other)Follow-up patch | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (own) | partition -> partitioned | about 8 years ago |
| Started threadFirst patch | partition -> partitioned | about 8 years ago |
| Replied (other)Follow-up patch | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | Indexes on partitioned tables and foreign partitions | about 8 years ago |
| Replied (other) | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (own) | \d doesn't show partitioned table foreign keys | about 8 years ago |
| Replied (other) | Incorrect comment in get_partition_dispatch_recurse | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (own)Follow-up patch | \d doesn't show partitioned table foreign keys | about 8 years ago |
| Started threadFirst patch | \d doesn't show partitioned table foreign keys | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | Postgres 11 release notes | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other) | Needless additional partition check in INSERT? | about 8 years ago |
| Replied (other)Follow-up patch | Indexes on partitioned tables and foreign partitions | about 8 years ago |
| Replied (other) | Indexes on partitioned tables and foreign partitions | about 8 years ago |
| Replied (other) | Indexes on partitioned tables and foreign partitions | about 8 years ago |
| Replied (own) | path toward faster partition pruning | about 8 years ago |
| Replied (other)Follow-up patch | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (own)Follow-up patch | path toward faster partition pruning | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (own) | path toward faster partition pruning | about 8 years ago |
| Replied (own)Follow-up patch | path toward faster partition pruning | about 8 years ago |
| Replied (own) | path toward faster partition pruning | about 8 years ago |
| Replied (own)Follow-up patch | no partition pruning when partitioning using array type | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other)Follow-up patch | Remove mention in docs that foreign keys on partitioned tables are not supported | about 8 years ago |
| Replied (other) | Local partitioned indexes and pageinspect | about 8 years ago |
| Replied (other) | Local partitioned indexes and pageinspect | about 8 years ago |
| Replied (own) | stats_ext test fails with -DCATCACHE_FORCE_RELEASE | about 8 years ago |
| Replied (other) | Remove mention in docs that foreign keys on partitioned tables are not supported | about 8 years ago |
| Replied (other) | Oddity in tuple routing for foreign partitions | about 8 years ago |
| Replied (own) | minor fix for acquire_inherited_sample_rows | about 8 years ago |
| Replied (other) | Should we add GUCs to allow partition pruning to be disabled? | about 8 years ago |
| Replied (other) | Re: [GENERAL] huge RAM use in multi-command ALTER of table heirarchy | about 8 years ago |
| Started threadFirst patch | stats_ext test fails with -DCATCACHE_FORCE_RELEASE | about 8 years ago |
| Replied (other) | FOR EACH ROW triggers on partitioned tables | about 8 years ago |