| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | krujkov(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15857: Parallel Hash Join makes join instead of exists |
| Date: | 2019-06-18 11:17:07 |
| Message-ID: | CA+hUKGKcPcayiknzwx5BAo41cs-ymtLk6b8Ebg7fjXsVMvmcUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jun 18, 2019 at 9:24 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> That points to the problem: for JOIN_UNIQUE_INNER we plan a Parallel
> Hash Join, but that's nonsense, there is no code to unique-ify the
> partial inner side (because that's not possible). There may be
> something better we can do here (like understanding that this should
> really be a semi-join), but this works for me to prevent the bad plan:
Here's a tidier version with a comment and commit message.
--
Thomas Munro
https://enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Prevent-Parallel-Hash-Join-for-JOIN_UNIQUE_INNER.patch | application/octet-stream | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Ferreira | 2019-06-18 11:28:35 | Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0” |
| Previous Message | PG Bug reporting form | 2019-06-18 10:02:53 | BUG #15858: could not stat file - over 4GB |