Partial join - Mailing list pgsql-hackers

From Arne Roland
Subject Partial join
Date
Msg-id dd01626a46a342f7b1d811cf38fcebe6@index.de
Whole thread Raw
Responses Re: Partial join  (Richard Guo <riguo@pivotal.io>)
List pgsql-hackers
Hello,

I attached one example of a partitioned table with multi column partition key. I also attached the output.
Disabling the hash_join is not really necessary, it just shows the more drastic result in the case of low work_mem.

Comparing the first and the second query I was surprised to see that SET enable_partitionwise_join could cause the costs to go up. Shouldn't the paths of the first query be generated as well?

The third query seems to have a different issue. That one is close to my original performance problem. It looks to me like the push down of the sl condition stops the optimizer considering a partial join.
If so would it be sane to keep a copy of the original quals to make the partial join possible? Do you have better ideas?


Regards
Arne
Attachment

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: How to retain lesser paths at add_path()?
Next
From: Thomas Munro
Date:
Subject: Re: using explicit_bzero