| Replied (other) | 11.7. Indexes on Expressions | over 4 years ago |
| Replied (own) | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (other) | When Update balloons memory | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | track_io_timing default setting | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other)First patch | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | Add index scan progress to pg_stat_progress_vacuum | over 4 years ago |
| Replied (other) | Add index scan progress to pg_stat_progress_vacuum | over 4 years ago |
| Replied (own)Follow-up patch | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL | over 4 years ago |
| Replied (other) | Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL | over 4 years ago |
| Replied (other) | Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL | over 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | parallel vacuum comments | over 4 years ago |
| Replied (other) | generalized conveyor belt storage | over 4 years ago |
| Replied (other) | When Update balloons memory | over 4 years ago |
| Replied (other) | When Update balloons memory | over 4 years ago |
| Replied (own) | Defining (and possibly skipping) useless VACUUM operations | over 4 years ago |
| Replied (other) | When Update balloons memory | over 4 years ago |
| Replied (own) | Defining (and possibly skipping) useless VACUUM operations | over 4 years ago |
| Started thread | Defining (and possibly skipping) useless VACUUM operations | over 4 years ago |
| Replied (own) | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (other) | BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum | over 4 years ago |
| Replied (other) | BUG #17255: Server crashes in index_delete_sort_cmp() due to race condition with vacuum | over 4 years ago |
| Replied (own) | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (own) | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (own) | Unifying VACUUM VERBOSE and log_autovacuum_min_duration output | over 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | BUG #17330: EXPLAIN hangs and very long query plans | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (own) | Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (own) | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Started thread | Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically? | over 4 years ago |
| Replied (other) | Skip vacuum log report code in lazy_scan_heap() if possible | over 4 years ago |
| Replied (own) | Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? | over 4 years ago |
| Replied (own)First patch | Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? | over 4 years ago |
| Started threadFirst patch | Deprecating the term "super-exclusive lock" | over 4 years ago |