From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "martin(dot)querleu(at)effisys(dot)fr" <martin(dot)querleu(at)effisys(dot)fr> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Update on |
Date: | 2020-11-27 18:30:53 |
Message-ID: | CAKFQuwZjQF3fmdTUqQ6nsZkDhN0azLvnn+Oecgvk7_7GcYoakw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Friday, November 27, 2020, EffiSYS / Martin Querleu <
martin(dot)querleu(at)effisys(dot)fr> wrote:
> Hello
>
> We use PG 11.9 and are encountering the problem with connection limit and
> parallel workers aborting a totally valid query ("CONTEXT: parallel worker"
> error)
>
> I found there was a thread concerning this problem and even a patch was
> developed: https://www.postgresql.org/message-id/CAB7nPqQKJPgNkg0VQguUP
> 1u%2BpDdk1qF16Qh5MtDQEtSMG4S-fg%40mail.gmail.com but no news since 2017
>
> Do you know the status of the patch or a modification to remove the
> parallel worker from the connection count against user (also server?)
> CONNECTION_LIMIT or to just not launch workers if not possible?
That thread was resolved with a committed patch [1] mid-thread, then got
hijacked a bit...
https://github.com/postgres/postgres/commit/f1169ab501ce90e035a7c6489013a1d4c250ac92
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-11-27 19:07:42 | Re: BUG #16749: EXPLAIN only shows filtering from the first query in a union chain when using distinct on. |
Previous Message | EffiSYS / Martin Querleu | 2020-11-27 18:22:55 | Update on |