| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | over 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Started thread | pgsql: vacuumlazy.c: Remove obsolete num_tuples field. | over 4 years ago |
| Started thread | pgsql: Remove unnecessary heap_tuple_needs_freeze argument. | over 4 years ago |
| Replied (other) | [PATCH] add relation and block-level filtering to pg_waldump | over 4 years ago |
| Replied (other) | Add index scan progress to pg_stat_progress_vacuum | over 4 years ago |
| Replied (other) | small development tip: Consider using the gold linker | 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 (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | BUG #17406: Segmentation fault on GiST index after 14.2 upgrade | over 4 years ago |
| Replied (own) | Time to increase hash_mem_multiplier default? | over 4 years ago |
| Started thread | pgsql: Increase hash_mem_multiplier default to 2.0. | over 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Started thread | pgsql: Avoid VACUUM reltuples distortion. | 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) | Lowering the ever-growing heap->pd_lower | 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 (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 |
| Started thread | pgsql: Update "don't truncate with failsafe" rationale. | over 4 years ago |
| Replied (other) | adding 'zstd' as a compression algorithm | over 4 years ago |
| Replied (other) | adding 'zstd' as a compression algorithm | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (own) | Time to increase hash_mem_multiplier default? | over 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | over 4 years ago |
| Replied (other) | Possible to go without page headers? | over 4 years ago |
| Started threadFirst patch | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | over 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Started thread | pgsql: Consolidate VACUUM xid cutoff logic. | over 4 years ago |
| Started thread | pgsql: Add VACUUM instrumentation for scanned pages, relfrozenxid. | over 4 years ago |
| Started thread | pgsql: Simplify lazy_scan_heap's handling of scanned pages. | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | pg_walinspect - a new extension to get raw WAL data and WAL stats | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | over 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | over 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | over 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | over 4 years ago |
| Replied (other) | decoupling table and index vacuum | over 4 years ago |
| Replied (own) | Stats collector's idx_blks_hit value is highly misleading in practice | over 4 years ago |
| Replied (own) | Why is INSERT-driven autovacuuming based on pg_class.reltuples? | over 4 years ago |