| Replied (other) | Problem with default partition pruning | over 6 years ago |
| Replied (other)Follow-up patch | partition routing layering in nodeModifyTable.c | over 6 years ago |
| Replied (other) | advanced partition matching algorithm for partition-wise join | over 6 years ago |
| Replied (other) | BUG #15933: Partition by multiple columns bug | over 6 years ago |
| Replied (other) | Runtime pruning problem | over 6 years ago |
| Replied (other) | Attached partition not considering altered column properties of root partition. | over 6 years ago |
| Replied (other) | CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? | over 6 years ago |
| Replied (other)Follow-up patch | partition routing layering in nodeModifyTable.c | over 6 years ago |
| Replied (other)Follow-up patch | Attached partition not considering altered column properties of root partition. | over 6 years ago |
| Replied (other)First patch | partition routing layering in nodeModifyTable.c | over 6 years ago |
| Replied (other) | partition routing layering in nodeModifyTable.c | over 6 years ago |
| Replied (other) | partition routing layering in nodeModifyTable.c | over 6 years ago |
| Replied (own)Follow-up patch | d25ea01275 and partitionwise join | over 6 years ago |
| Replied (other)Follow-up patch | CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? | over 6 years ago |
| Replied (other) | Change ereport level for QueuePartitionConstraintValidation | almost 7 years ago |
| Replied (other) | PG11 - Multiple Key Range Partition | almost 7 years ago |
| Replied (other) | [RFC] [PATCH] Flexible "partition pruning" hook | almost 7 years ago |
| Replied (other) | PG11 - Multiple Key Range Partition | almost 7 years ago |
| Replied (other) | Excessive memory usage in multi-statement queries w/ partitioning | almost 7 years ago |
| Replied (other) | Excessive memory usage in multi-statement queries w/ partitioning | almost 7 years ago |
| Replied (other) | PG11 - Multiple Key Range Partition | almost 7 years ago |
| Replied (other) | FDW does not push down LIMIT & ORDER BY with sharding (partitions) | almost 7 years ago |
| Replied (other)Follow-up patch | Excessive memory usage in multi-statement queries w/ partitioning | almost 7 years ago |
| Replied (other) | Postgres 11: Table Partitioning and Primary Keys | almost 7 years ago |
| Replied (other) | CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? | almost 7 years ago |
| Replied (other) | Postgres 11: Table Partitioning and Primary Keys | almost 7 years ago |
| Replied (other) | FDW does not push down LIMIT & ORDER BY with sharding (partitions) | almost 7 years ago |
| Replied (other)Follow-up patch | Excessive memory usage in multi-statement queries w/ partitioning | almost 7 years ago |
| Replied (other) | Broken defenses against dropping a partitioning column | almost 7 years ago |
| Replied (other) | Run-time pruning for ModifyTable | almost 7 years ago |
| Replied (other) | Another way to fix inherited UPDATE/DELETE | almost 7 years ago |
| Replied (other) | Run-time pruning for ModifyTable | almost 7 years ago |
| Replied (other) | Problem with default partition pruning | almost 7 years ago |
| Replied (other) | Another way to fix inherited UPDATE/DELETE | almost 7 years ago |
| Replied (other) | Run-time pruning for ModifyTable | almost 7 years ago |
| Replied (other)First patch | Attached partition not considering altered column properties of root partition. | almost 7 years ago |
| Started threadFirst patch | d25ea01275 and partitionwise join | almost 7 years ago |