Re: [HACKERS] walsender & parallelism
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] walsender & parallelism |
Дата | |
Msg-id | b0cae230-066c-d5ee-b2d7-29ba44c142bb@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] walsender & parallelism (Petr Jelinek <petr.jelinek@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] walsender & parallelism
Re: [HACKERS] walsender & parallelism |
Список | pgsql-hackers |
On 5/23/17 13:57, Petr Jelinek wrote: > On 23/05/17 19:45, Andres Freund wrote: >> >> >> On May 23, 2017 1:42:41 PM EDT, Petr Jelinek <petr.jelinek@2ndquadrant.com> wrote: >>> Hi, >>> >>> so this didn't really move anywhere AFAICS, do we think the approach >>> I've chosen is good or do we want to do something else here? >> >> Can you add it to the open items list? >> > > Done I think the easiest and safest thing to do now is to just prevent parallel plans in the walsender. See attached patch. This prevents the hang in the select_parallel tests run under your new test setup. Unifying the signal handling and query processing further seems like a good idea, but the patches are pretty involved, so I suggest to put them into the next commit fest. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: