| From: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
|---|---|
| To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transaction timeout |
| Date: | 2022-12-03 17:41:04 |
| Message-ID: | CAAhFRxg7p+Z=xAFAdPeuLeOvc+3DyKKJtg8PKfdE453yybfHMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 2, 2022 at 10:59 PM Nikolay Samokhvalov
<samokhvalov(at)gmail(dot)com> wrote:
>
> But it fails in the "worst" case I've described above – a series of small statements:
Fixed. Added test for this.
Open questions:
1. Docs
2. Order of reporting if happened lock_timeout, statement_timeout, and
transaction_timeout simultaneously. Currently there's a lot of code
around this...
Thanks!
Best regards, Andrey Borodin.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Intorduce-transaction_timeout.patch | application/octet-stream | 11.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-12-03 18:17:22 | Re: Replace PROC_QUEUE / SHM_QUEUE with ilist.h |
| Previous Message | Matheus Alcantara | 2022-12-03 17:34:57 | Re: mprove tab completion for ALTER EXTENSION ADD/DROP |