| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | dinesh kumar <dineshkumar02(at)gmail(dot)com>, Justin <zzzzz(dot)graf(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FATAL Idle transaction timeout - TRX Commit |
| Date: | 2026-09-05 13:29:29 |
| Message-ID: | CAKAnmmL79o9Wwzft3gEPnbnHbuRTge9FjNLW60h_E6ni8+TFZQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
This is not a normal FATAL from the server - that particular message is
coming from pgcat, not from Postgres. So the normal FATAL/connection
terminated/reconnect flow is not relevant here, as it is pgcat that is
responsible for all this. The FATAL is being sent to the client only -
pgcat is probably releasing that connection and fetching you a new one in
the background. Try tweaking your idle_client_in_transaction_timeout
setting in your pgcat config to duplicate/debug the behavior, and sprinkle
some pg_backend_pid() calls in there.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Long Dang Ngoc | 2026-09-07 02:13:38 | Atomic idempotency for external API dispatch with PostgreSQL and Celery |
| Previous Message | Christophe Pettus | 2026-09-05 04:18:00 | Re: FATAL Idle transaction timeout - TRX Commit |