Postgres Pro
Downloads
Home   >   mailing lists

Warning for exceeding max locks? - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Warning for exceeding max locks?
Date
Msg-id 4699760F.1010109@commandprompt.com
Whole thread Raw
Responses Re: Warning for exceeding max locks?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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/

pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: has anyone looked at burstsort ?
Next
From: Tom Lane
Date:
Subject: Re: Warning for exceeding max locks?