From: | James Robinson <jlrobins(at)socialserve(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | no-arg cluster and locks ... |
Date: | 2008-02-24 22:38:49 |
Message-ID: | 87AD0987-FE15-4312-9F6C-4810AFA532D7@socialserve.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
How does 8.2 [ or 8.3 ] deal with table locking in the face of no-
argument 'cluster' command? Does it lock all tables it is going to
visit 'up front', or does it collect locks slowly as it visits
tables? If it only locks a new table before it visits it, does it
unlock it once it is done?
Finally, is it a candidate for deadlock detection and unrolling just
as other locking ops are [ I can imagine one wouldn't want to
deadlock-kill the clustering backend, but the backend it contends
with might be fodder assuming its a lesser command ].
We just some observed an undetected deadlock-ish issue, and the
juciest aspect was that a db-wide cluster was running.
Thanks!
----
James Robinson
Socialserve.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-24 22:39:27 | Re: plpgsql function |
Previous Message | Joris Dobbelsteen | 2008-02-24 22:35:41 | Planner: rows=1 after "similar to" where condition. |