On 4/23/15 8:25 AM, Robert Haas wrote:
> Some users are partitioning tables just so that each
> partition can be autovac'd separately. That really shouldn't be
> required.
Are they doing this for improved heap scan performance? Index scan
performance? If the table wasn't partitioned, would they need more than
one pass through the indexes due to exhausting maintenance_work_mem?
There's probably some fairly low-hanging fruit for parallelizing vacuum,
but it really depends on what problems people are running into.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com