> It's used to trigger ETL jobs. There are other bigger consumers of > connections - the issue isn't the stream of jobs, that works fine under > normal operation. The issue is that when jobs stay in "startup" and > don't enter pg_stat_activity the system spirals downwards and no new > connections are allowed.
Is there a correlation to these ETL jobs or the other consumers?
If so what are the consumers trying to do at that time?
Not really no - it seems to be pretty randomly timed.
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.
