Shaun Thomas wrote:
...
> The really strange thing is, one of our newwer databases has
> started hanging on vacuums. That's a 7.1.1, so the 8k thing shouldn't be
> any kind of issue in the slightest thanks to the new internal structures.
>
> But something is corrupt enough to break vaccum badly. That doesn't make
> me feel very good. The worst part is, while it's hung on the vacuum, idle
> connections just start piling up until we have to restart the DB.
That is probably an issue with one of your applications keeping an
open transaction against the table vacuum is attempting to access:
In Session #1:
BEGIN;
SELECT * FROM employees;
In Session #2:
VACUUM employees; <---- VACUUM is waiting on Session #1
In Session #3:
SELECT * FROM employees; <--- Now waiting because of VACUUM
In Session #1:
END;
You will see the Session #2 VACUUM complete and then the Session #3
SELECT complete. You've got some broken client app that needs to
either COMMIT or ABORT.
Hope that helps,
Mike Mascari
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
