Atri Sharma <atri.j...@gmail.com> writes: >> For instance, take out exclusive locks on all your tables and just >> go to sleep (although I think this is limited by table permissions in >> recent PG versions).
> This is what I have been worried about. The locks(exclusive locks or > content locks in buffers) can be held and stalled. Cant we do anything > about it? This is why I contemplated the timeout part. No, you're not following. These would be table-level heavyweight locks, and there already are timeout mechanisms that work at that level. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers