| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: walsender & parallelism |
| Date: | 2017-06-02 02:17:57 |
| Message-ID: | 48aed7ec-ae32-6ef2-102d-eea8545bda77@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/1/17 00:06, Andres Freund wrote:
> On 2017-05-31 23:51:08 -0400, Peter Eisentraut wrote:
>> 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.
> I'm not quite sure I can buy this. The lack of wired up signals has
> more problems than just hurting parallelism.
Which problems are those? I can see from the code what they might be,
but which ones actually happen in practice? And are there any
regressions from 9.6?
If someone wants to work all this out, that would be great. But I'm
here mainly to fix the one reported problem.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2017-06-02 02:18:30 | Re: BUG #14682: row level security not work with partitioned table |
| Previous Message | Tom Lane | 2017-06-02 02:05:09 | Re: Patch: Add --no-comments to skip COMMENTs with pg_dump |