Warning for exceeding max locks?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Warning for exceeding max locks?
Date: 2007-07-15 01:19:11
Message-ID: 4699760F.1010109@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

We ran into a problem with a customer this weekend. They had >128,000
tables and we were trying to run a pg_dump. When we reached
max_locks_per_transaction, the dump just hung waiting to lock the next
table.

Would it make sense to have some sort of timeout for that?

wait_for_lock_timeout?

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-07-15 02:23:24 Re: Warning for exceeding max locks?
Previous Message Martijn van Oosterhout 2007-07-15 01:15:56 Re: has anyone looked at burstsort ?