| From: | James Sewell <james(dot)sewell(at)jirotech(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Max connections reached without max connections reached |
| Date: | 2021-12-03 01:29:49 |
| Message-ID: | CAANVwEtQtPcuLMdHVoio0kQJQnYKxSfOTnuTaE2cQ4X+RdE+Jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sonai muthu raja M | 2021-12-03 04:05:01 | Re: Require details that how to find user creation date in postgresql Database |
| Previous Message | Paul van der Linden | 2021-12-02 23:20:05 | Re: CTE Materialization |