| From: | dinesh kumar <dineshkumar02(at)gmail(dot)com> |
|---|---|
| To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | FATAL Idle transaction timeout - TRX Commit |
| Date: | 2026-09-04 20:24:00 |
| Message-ID: | CALnrH7qJAs0cA58EGj5gz4mwxb-3Zg47dzjCvyRp7cfdHA03nw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
During one of our recent database maintenance windows, we found strange
behaviour.
rupeecom=*> SELECT id FROM owuhhrlb.orders order by order_time desc limit
10;
id
------------
2867948821
6692427082
5676641762
2129769831
9491447513
9208637522
7331803655
1763525242
9609866278
0442784132
(10 rows)
*rupeecom=*> DELETE FROM owuhhrlb.orders WHERE id IN (SELECT id FROM
owuhhrlb.orders order by order_time desc limit 10); *
*FATAL: idle transaction timeout*
*rupeecom=> *
*rupeecom=> BEGIN WORK;*
*DELETE 10*
As you see above, after the transaction terminated, the subsequent BEGIN
WORK; statement committed the previous transaction. We are using PostgreSQL
16.14, also we are using pgCat as connection pooler ...
--
Regards,
Dinesh
manojadinesh.blogspot.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2026-09-04 20:52:24 | introducing pgasync and pgflow |
| Previous Message | Justin | 2026-08-27 16:30:23 | Re: Why didn't I get an error in the Exception block? |