From: | James Sewell <james(dot)sewell(at)jirotech(dot)com> |
---|---|
To: | Amul Sul <sulamul(at)gmail(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-21 00:25:54 |
Message-ID: | CAANVwEsZf0Y1XR1ePtMu_aoHdAKFi3Z2TZzOqFPiUqD0n7a7ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Ok it is possible, I've got a C extension up and running which hooks
> ExecutorStart, then once for each TX ( I monitor the nesting depth like in
> pg_stat_statements, and only attach at the top level) attaches a sub
> transaction callback, tracking start subtransaction events and incrementing
> a counter / keeping track of the worst offenders in a hashmap.
>
Sorry that should be ExecutorRun - although I'm a little confused about
which is the correct choice.
-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 | Akheel Ahmed | 2021-12-21 05:09:19 | Sorting difference in version 10 vs 13 |
Previous Message | James Sewell | 2021-12-21 00:22:05 | Re: Max connections reached without max connections reached |