Hi,
<history>
Sometime back my app had some probs with postgres 7.1.2- the app did a lot
of updates, and somehow after weeks the backend exited when I did a select
on a table.
I truncated the table and updated to 7.1.3 (did not pg_dump).
I'm trying to see if the problem recurs in 7.1.3.
</history>
Recently I vacummed the database (the postmasters were using a lot of cpu).
No vacuum analyze, just plain psql, vacuum.
The disk usage before vacuuming was 95MB.
After dropped to 45MB.
Then I noticed the postmaster for a particular table still using lots of
cpu 45-80%. Another postmaster on the same database, using different table
was using a lot less cpu.
I vacuumed again, this time the troublesome table specifically.
Then the disk usage dropped to 9MB. And the postmaster cpu usage went down.
I did not restart the app or postgres.
Is it normal to require two vacuums for it to be effective? AFAIK I was
connected to the correct database when vacuuming.
Should I have pg_dumped and reloaded?
Regards,
Link.