| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Andrey Lizenko <lizenko79(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to monitor locks (max_pred_locks_per_transaction)? |
| Date: | 2015-01-09 20:04:57 |
| Message-ID: | 1325325919.4259646.1420833897790.JavaMail.yahoo@jws10031.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrey Lizenko <lizenko79(at)gmail(dot)com> wrote:
> does max_locks_per_transaction limit all others modes of locks by
> the same way?
In the sense that the count of all other locks must be less than
max_locks_per_transaction * max_connections, yes. Most other locks
do not persist past the end of transactions or the closing of
connections (advisory locks and locks related to prepared
transactions being edge-case exceptions). No other types of locks
have the granularity promotion -- most other locks showing in
sp_locks are on relations or transactions.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Nolan | 2015-01-09 22:14:11 | How to analyze a slowdown in 9.3.5? |
| Previous Message | dvlsg | 2015-01-09 19:44:55 | Re: PSQL/pgAdmin - Column Completion |