Skip site navigation (1) Skip section navigation (2)

Re: Join runs for > 10 hours and then fills up >1.3TB of disk space

From: kevin kempter <kevin(at)kevinkempterllc(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Join runs for > 10 hours and then fills up >1.3TB of disk space
Date: 2008-05-16 08:00:41
Message-ID: 8B5A9097-109E-45F5-A658-7FC723EA75F3@kevinkempterllc.com (view raw or flat)
Thread:
Lists: pgsql-performance
I'm expecting 9,961,914 rows returned. Each row in the big table  
should have a corresponding key in the smaller tale, I want to  
basically "expand" the big table column list by one, via adding the  
appropriate key from the smaller table for each row in the big table.  
It's not a cartesion product join.



On May 16, 2008, at 1:40 AM, Richard Huxton wrote:

> kevin kempter wrote:
>> Hi List;
>> I have a table with 9,961,914 rows in it (see the describe of  
>> bigtab_stats_fact_tmp14 below)
>> I also have a table with 7,785 rows in it (see the describe of  
>> xsegment_dim below)
>> I'm running the join shown below and it takes > 10 hours and  
>> eventually runs out of disk space on a 1.4TB file system
>
>> QUERY PLAN
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Merge 
>>  Join  (cost=1757001.74..73569676.49 rows=3191677219 width=118)
>
> Dumb question Kevin, but are you really expecting 3.2 billion rows  
> in the result-set? Because that's approaching 400GB of result-set  
> without any overheads.
>
> -- 
>  Richard Huxton
>  Archonet Ltd


In response to

Responses

pgsql-performance by date

Next:From: Richard HuxtonDate: 2008-05-16 08:16:19
Subject: Re: Join runs for > 10 hours and then fills up >1.3TB of disk space
Previous:From: Richard HuxtonDate: 2008-05-16 07:40:16
Subject: Re: Join runs for > 10 hours and then fills up >1.3TB of disk space

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group