[PERFORM] vacuumdb command

Hi I used the vacuumdb command. But in its output I cann't see VACUUM. The last part of output is DETAIL: 0 dead row versions cannot be removed yet. There were 0 unused item pointers. 1 pages contain useful free space. 0 pages are entirely empty. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: fre

Re: [PERFORM] vacuumdb command

soorjith p wrote: > I used the vacuumdb command. But in its output I cann't see VACUUM. > > The last part of output is > > DETAIL: 0 dead row versions cannot be removed yet. > There were 0 unused item pointers. > 1 pages contain useful free space. > 0 pages are entirely empty. > CPU 0.00s/0.00u

Re: [PERFORM] table partitioning & max_locks_per_transaction

Tom -- Thanks for the pointers and advice. We've started by doubling max_locks and halving shared_buffers, we'll see how it goes. Brian On Oct 10, 2009, at 7:56 PM, Tom Lane wrote: Brian Karlak writes: "out of shared memory HINT: You might need to increase max_locks_per_transa