Re: Max connections reached without max connections reached - Mailing list pgsql-general

From James Sewell
Subject Re: Max connections reached without max connections reached
Date
Msg-id CAANVwEtQtPcuLMdHVoio0kQJQnYKxSfOTnuTaE2cQ4X+RdE+Jw@mail.gmail.com
Whole thread Raw
In response to Re: Max connections reached without max connections reached  (Michael Lewis <mlewis@entrata.com>)
List pgsql-general
I expect my 'vote' counts for naught, but I fully expect seeing these show up in the logs would have helped me much more quickly have insight into what was going on during times of very high concurrency and extreme slowness with many processes showing as waiting on LwLocks.

Is there any mechanism I could use from a C extension and a hook to warn about >64 overflows? 

- James


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

pgsql-general by date:

Previous
From: Paul van der Linden
Date:
Subject: Re: CTE Materialization
Next
From: "Sonai muthu raja M"
Date:
Subject: Re: Require details that how to find user creation date in postgresql Database