| Replied (own) | Account for cost and selectivity of HAVING quals | over 8 years ago |
| Replied (other) | PostgreSQL 10 parenthesized single-column updates can produce errors | over 8 years ago |
| Replied (other) | PostgreSQL 10 parenthesized single-column updates can produce errors | over 8 years ago |
| Started threadFirst patch | Account for cost and selectivity of HAVING quals | over 8 years ago |
| Replied (other)Follow-up patch | PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM | over 8 years ago |
| Replied (other) | PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM | over 8 years ago |
| Replied (other) | SQL procedures | over 8 years ago |
| Replied (other) | Fix dumping pre-10 DBs by pg_dump10 if table "name" exists | over 8 years ago |
| Replied (other) | PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM | over 8 years ago |
| Replied (other) | Fix dumping pre-10 DBs by pg_dump10 if table "name" exists | over 8 years ago |
| Replied (other) | Add some const decorations to prototypes | over 8 years ago |
| Replied (other) | Query regarding permission on table_column%type access | over 8 years ago |
| Replied (other) | PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM | over 8 years ago |
| Replied (other) | PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM | over 8 years ago |
| Replied (other) | BUG #14883: Syntax SQL error (42601), but should be a different error no | over 8 years ago |