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 CAANVwEsZf0Y1XR1ePtMu_aoHdAKFi3Z2TZzOqFPiUqD0n7a7ug@mail.gmail.com
Whole thread Raw
In response to Re: Max connections reached without max connections reached  (James Sewell <james.sewell@jirotech.com>)
List 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.

pgsql-general by date:

Previous
From: James Sewell
Date:
Subject: Re: Max connections reached without max connections reached
Next
From: Akheel Ahmed
Date:
Subject: Sorting difference in version 10 vs 13