| Replied (own)Follow-up patch | More reliable nbtree detection of unsatisfiable RowCompare quals involving a leading NULL key/element | over 1 year ago |
| Replied (own) | nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID | over 1 year ago |
| Replied (own) | nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID | over 1 year ago |
| Started threadFirst patch | More reliable nbtree detection of unsatisfiable RowCompare quals involving a leading NULL key/element | over 1 year ago |
| Replied (own) | Bug in nbtree SAOP scans with non-required arrays, truncated high key | over 1 year ago |
| Started threadFirst patch | Bug in nbtree SAOP scans with non-required arrays, truncated high key | over 1 year ago |
| Replied (other) | Exceptional md.c paths for recovery and zero_damaged_pages | over 1 year ago |
| Replied (other) | Exceptional md.c paths for recovery and zero_damaged_pages | over 1 year ago |
| Replied (other) | Exceptional md.c paths for recovery and zero_damaged_pages | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? | over 1 year ago |
| Replied (other) | bt_index_parent_check and concurrently build indexes | over 1 year ago |
| Replied (own)Follow-up patch | Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) | over 1 year ago |
| Replied (own)Follow-up patch | Adding skip scan (including MDAM style range skip scan) to nbtree | over 1 year ago |
| Replied (other) | Dangling operator family after DROP TYPE | over 1 year ago |
| Replied (own) | Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (own)Follow-up patch | Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other)Follow-up patch | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | Incorrect result of bitmap heap scan. | over 1 year ago |
| Replied (other) | backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST | over 1 year ago |
| Replied (other) | backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST | over 1 year ago |