| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | about 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (other) | [PATCH] add relation and block-level filtering to pg_waldump | about 4 years ago |
| Replied (other) | Add index scan progress to pg_stat_progress_vacuum | about 4 years ago |
| Replied (other) | small development tip: Consider using the gold linker | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | BUG #17406: Segmentation fault on GiST index after 14.2 upgrade | about 4 years ago |
| Replied (own) | Time to increase hash_mem_multiplier default? | about 4 years ago |
| Replied (own) | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | Lowering the ever-growing heap->pd_lower | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | adding 'zstd' as a compression algorithm | about 4 years ago |
| Replied (other) | adding 'zstd' as a compression algorithm | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (own) | Time to increase hash_mem_multiplier default? | about 4 years ago |
| Replied (other) | do only critical work during single-user vacuum? | about 4 years ago |
| Replied (other) | Possible to go without page headers? | about 4 years ago |
| Started threadFirst patch | Nonrandom scanned_pages distorts pg_class.reltuples set by VACUUM | about 4 years ago |
| Replied (own)Follow-up patch | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | pg_walinspect - a new extension to get raw WAL data and WAL stats | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | about 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | about 4 years ago |
| Replied (other) | BUG #17401: REINDEX TABLE CONCURRENTLY creates a race condition on a streaming replica | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (own) | Removing more vacuumlazy.c special cases, relfrozenxid optimizations | about 4 years ago |
| Replied (other) | should vacuum's first heap pass be read-only? | about 4 years ago |
| Replied (other) | decoupling table and index vacuum | about 4 years ago |
| Replied (own) | Stats collector's idx_blks_hit value is highly misleading in practice | about 4 years ago |
| Replied (own) | Why is INSERT-driven autovacuuming based on pg_class.reltuples? | about 4 years ago |