From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parallelize queries containing initplans |
Date: | 2017-10-05 12:38:00 |
Message-ID: | CA+Tgmoa0JJS-6SBZA5-5PtMdiTnF1s9EwgbdpTnFTYnn0fvogw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 5, 2017 at 5:52 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Now, unless, I am missing something here, it won't be possible to
> detect params in such cases during forming of join rels and hence we
> need the tests in generate_gather_paths. Let me know if I am missing
> something in this context or if you have any better ideas to make it
> work?
Hmm, in a case like this, I think we shouldn't need to detect it. The
Var is perfectly parallel-safe, the problem is that we can't use a
not-safe plan for the inner rel. I wonder why that's happening
here... is it a problem with your patch or an existing bug?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-10-05 12:38:35 | Re: cache lookup errors for missing replication origins |
Previous Message | Kyotaro HORIGUCHI | 2017-10-05 12:02:41 | Re: Logging idle checkpoints |