| From: | Kris Jurka <books(at)ejurka(dot)com> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: No hash join across partitioned tables? | 
| Date: | 2009-04-16 23:30:51 | 
| Message-ID: | Pine.BSO.4.64.0904161921080.11937@leary.csoft.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance | 
On Thu, 16 Apr 2009, Tom Lane wrote:
> Kris Jurka <books(at)ejurka(dot)com> writes:
>> PG (8.3.7) doesn't seem to want to do a hash join across two partitioned
>> tables.
>
> Could we see the whole declaration of these tables?  (pg_dump -s output
> would be convenient)
>
The attached table definition with no data wants to mergejoin first, but 
after disabling mergejoin it does indeed do a hashjoin.
Looking back at the cost estimates for the merge and nestloop joins, it 
seems to be selecting the number of rows in the cartesian product * .005 
while the number of output rows in this case is 2437 (cartesian product * 
4e-9).  Perhaps the cost estimates for the real data are so high because 
of this bogus row count that the fudge factor to disable mergejoin isn't 
enough?
Kris Jurka
| Attachment | Content-Type | Size | 
|---|---|---|
| hash-join-partition.sql | text/plain | 2.5 KB | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-04-17 00:28:43 | Re: HashJoin w/option to unique-ify inner rel | 
| Previous Message | Tom Lane | 2009-04-16 23:26:52 | Re: HashJoin w/option to unique-ify inner rel | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Figueiredo Jr. | 2009-04-16 23:43:20 | Re: need information | 
| Previous Message | Tom Lane | 2009-04-16 23:12:11 | Re: No hash join across partitioned tables? |