Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Robert Haas <robertmhaas@gmail.com>, Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-07-04T10:11:35Z
Lists: pgsql-hackers
On Wed, Jul 4, 2018 at 3:36 PM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > > I don't produce a test case where the plan is an Append with Gather > subplans, but I'm not sure that it's a good thing to allow us to consider > such a plan because in that plan, each Gather would try to grab its own pool > of workers. Am I missing something? If the overall join can not use parallelism, having individual child joins use parallel query might turn out to be efficient even if done one child at a time. Parallel append drastically reduces the cases where something like could be useful, but I don't think we can theoretically eliminate the need for such a plan. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Adjust EXPLAIN's output for disabled nodes
- 161320b4b960 18.0 cited
-
Disable support for partitionwise joins in problematic cases.
- 940487956ede 11.0 landed
- 7cfdc77023ad 12.0 landed
-
Rewrite the code that applies scan/join targets to paths.
- 11cf92f6e2e1 11.0 cited