| From: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
|---|---|
| To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Transaction timeout |
| Date: | 2022-12-03 05:18:40 |
| Message-ID: | CAAhFRxiQsRs2Eq5kCo9nXE3HTugsAAJdSQSmxncivebAxdmBjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
We have statement_timeout, idle_in_transaction_timeout,
idle_session_timeout and many more! But we have no
transaction_timeout. I've skimmed thread [0,1] about existing timeouts
and found no contraindications to implement transaction_timeout.
Nikolay asked me if I can prototype the feature for testing by him,
and it seems straightforward. Please find attached. If it's not known
to be a bad idea - we'll work on it.
Thanks!
Best regards, Andrey Borodin.
[0] https://www.postgresql.org/message-id/flat/763A0689-F189-459E-946F-F0EC4458980B%40hotmail.com
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Intorduce-transaction_timeout.patch | application/octet-stream | 9.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2022-12-03 06:58:19 | docs: add missing <varlistentry> id elements for developer GUCs |
| Previous Message | Amit Kapila | 2022-12-03 05:07:12 | Re: Avoid streaming the transaction which are skipped (in corner cases) |