| From: | Doug Reynolds <mav(at)wastegate(dot)net> |
|---|---|
| To: | Sbob <sbob(at)quadratum-braccas(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Quartz Scheduler + pgpool + PostgreSQL 12 = issues |
| Date: | 2022-06-30 23:29:08 |
| Message-ID: | 01000181b6f26940-f565d242-ccf8-4931-b5c2-081f7930f7cb-000000@email.amazonses.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Your developers need to fix the connection leaking in their Quartz scheduler code. Most likely, they aren’t releasing the connection.
Sent from my iPhone
> On Jun 30, 2022, at 7:19 PM, Sbob <sbob(at)quadratum-braccas(dot)com> wrote:
>
> All;
>
>
> I have a client that was using pgbouncer and PostgreSQL 12 relatively issue free, they recently deployed the quartz scheduler and now the db is running out of max_connections on a regular basis. I have an outage scheduled to increase max_connections but I am concerned that quartz will simply use them up.
>
>
> Has anyone else run into this? know of any fixes?
>
>
> Thanks in advance
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Shetty | 2022-07-01 07:41:38 | Re: Long running backup preventing auto vacuum |
| Previous Message | Sbob | 2022-06-30 23:18:58 | Quartz Scheduler + pgpool + PostgreSQL 12 = issues |