Out of Shared Memory: max_locks_per_transaction

Поиск
Список
Период
Сортировка
От Eliot Gable
Тема Out of Shared Memory: max_locks_per_transaction
Дата
Msg-id CAD-6L_WM1UTE+9375HWhj5i8J4H-W_sS4FJe7d1+NiBw_82jnw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Out of Shared Memory: max_locks_per_transaction  (Merlin Moncure <mmoncure@gmail.com>)
Список pgsql-general
I have a PGSQL 9.0.1 database which is on the back-end of an app I was stress testing last night. This morning, when I try to run psql, I get:

psql: FATAL:  out of shared memory
HINT:  You might need to increase max_locks_per_transaction.

I believe something in the app is failing to release resources -- maybe a 3-way or 4-way deadlock between writing to tables inside the triggers in PGSQL or a deadlock between multiple processes talking to the app and the database or something leaking in the app itself which is causing locks to not be freed. 

How do I track down what is going on if I cannot even run psql to get into the DB to run troubleshooting queries?

Thanks in advance for any suggestions.


--
Eliot Gable

"We do not inherit the Earth from our ancestors: we borrow it from our children." ~David Brower

"I decided the words were too conservative for me. We're not borrowing from our children, we're stealing from them--and it's not even considered to be a crime." ~David Brower

"Esse oportet ut vivas, non vivere ut edas." (Thou shouldst eat to live; not live to eat.) ~Marcus Tullius Cicero

В списке pgsql-general по дате отправления:

Предыдущее
От: Thalis Kalfigkopoulos
Дата:
Сообщение: Folder filenode in tablespace location not indentifiable by oid2name
Следующее
От: "Albe Laurenz"
Дата:
Сообщение: Re: Folder filenode in tablespace location not indentifiable by oid2name