waiting for lock?

From: Lennert Buytenhek <buytenh(at)gnu(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: waiting for lock?
Date: 2000-11-02 20:20:00
Message-ID: Pine.LNX.4.21.0011022119490.10715-100000@mara.math.leidenuniv.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Hi,

this evening I found a whole bunch of cron jobs hanging on a VACUUM of a
database. I killed them off and retried manually:

ulsec=> vacuum;
NOTICE: Skipping "pg_type" --- only table owner can VACUUM it
NOTICE: Skipping "pg_attribute" --- only table owner can VACUUM it
NOTICE: Skipping "pg_proc" --- only table owner can VACUUM it
NOTICE: Skipping "pg_class" --- only table owner can VACUUM it
NOTICE: Skipping "pg_indexes" --- only table owner can VACUUM it
NOTICE: Skipping "pg_group" --- only table owner can VACUUM it
NOTICE: Skipping "pg_database" --- only table owner can VACUUM it
NOTICE: Skipping "pg_attrdef" --- only table owner can VACUUM it
NOTICE: Skipping "pg_relcheck" --- only table owner can VACUUM it
NOTICE: Skipping "pg_trigger" --- only table owner can VACUUM it
NOTICE: Skipping "pg_inherits" --- only table owner can VACUUM it
NOTICE: Skipping "pg_index" --- only table owner can VACUUM it
NOTICE: Skipping "pg_statistic" --- only table owner can VACUUM it
NOTICE: Skipping "pg_operator" --- only table owner can VACUUM it
NOTICE: Skipping "pg_opclass" --- only table owner can VACUUM it
NOTICE: Skipping "pg_am" --- only table owner can VACUUM it
NOTICE: Skipping "pg_amop" --- only table owner can VACUUM it
NOTICE: Skipping "pg_amproc" --- only table owner can VACUUM it
NOTICE: Skipping "pg_language" --- only table owner can VACUUM it
NOTICE: Skipping "pg_aggregate" --- only table owner can VACUUM it
NOTICE: Skipping "pg_ipl" --- only table owner can VACUUM it
NOTICE: Skipping "pg_inheritproc" --- only table owner can VACUUM it
NOTICE: Skipping "pg_rewrite" --- only table owner can VACUUM it
NOTICE: Skipping "pg_listener" --- only table owner can VACUUM it
NOTICE: Skipping "pg_description" --- only table owner can VACUUM it
NOTICE: Skipping "pg_shadow" --- only table owner can VACUUM it
NOTICE: Skipping "pg_user" --- only table owner can VACUUM it
NOTICE: Skipping "pg_rules" --- only table owner can VACUUM it

And there it hangs.

strace reveals that the corresponding postgres process on the server hangs
on:

semop(10241, 0xbfffe924, 1

If you send psql a SIGINT, it returns with:

NOTICE: Skipping "pg_rules" --- only table owner can VACUUM it
Cancel request sent
ERROR: Query cancel requested while waiting lock
ulsec=>

When this happened, no other clients were accessing the database.
Restarting the server (postgresql 7.0.2) cured all. Anyone knows what's
going on there?

/Lennert

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2000-11-02 21:11:37 Re: waiting for lock?
Previous Message Thomas Lockhart 2000-11-02 18:18:22 Re: Bug in Time/Date routines