Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
От | Robert Haas |
---|---|
Тема | Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs) |
Дата | |
Msg-id | CA+TgmoYpJnM5vZC2BHS5mKXiDfk-xei=aZJuaAV1qDyTOcWztQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs) (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>) |
Ответы |
Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
|
Список | pgsql-hackers |
On Thu, Feb 4, 2016 at 11:55 AM, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote: > A query with FOR UPDATE/SHARE will be considered parallel unsafe in > has_parallel_hazard_walker() and root->glob->parallelModeOK will be marked > false. This implies that none of the base relations and hence join relations > will be marked as consider_parallel. IIUC your logic, none of the queries > with FOR UPDATE/SHARE will get a local path which is marked parallel_safe > and thus join will not be pushed down. Why do you think we need to skip > paths that aren't parallel_safe? I have left aside this change in the latest > patches. I changed this back before committing but, ah nuts, you're right. Sigh. Sorry. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: