"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> INFO: index "pg_toast_2144146_index" now contains 1971674 row versions
> in 10018 pages
> DETAIL: 4 index row versions were removed.
> 2489 index pages have been deleted, 0 are currently reusable.
> Just for the archives - I finally solved the pro
Jim C. Nasby wrote:
>>We started a VACUUM (not a VACUUM FULL) on one of your postgres 7.4.9
>>databases a few days ago. It's still running yet, and says the
>>folloing about once per second:
>>
>>INFO: index "pg_toast_2144146_index" now contains 1971674 row versions
>>in 10018 pages
>>DETAIL: 4
On Tue, November 29, 2005 0:37, Jim C. Nasby said:
> One issue is that pg_toast tables can't vacuum rows until their
> respective rows have been deleted by vacuuming the base table. But it's
> still odd that the count decreases by 4 each time you run it.
So, VACUUM would first vacuum , then
pg_toa
One issue is that pg_toast tables can't vacuum rows until their
respective rows have been deleted by vacuuming the base table. But it's
still odd that the count decreases by 4 each time you run it.
As for the length of time, that could be due to heavily loaded hardware.
You might do better if you
