Re: Table partition for very large table - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: Table partition for very large table
Date
Msg-id 20050328201831.GA5019@svana.org
Whole thread Raw
In response to Re: Table partition for very large table  (Yudie Gunawan <yudiepg@gmail.com>)
List pgsql-general
Looks like you need to create some indexes, probably on (groupnum) and
possibly on (groupnum,sku) on both tables.

Hope this helps,

On Mon, Mar 28, 2005 at 01:50:06PM -0600, Yudie Gunawan wrote:
> > Hold on, let's diagnose the real problem before we look for solutions.
> > What does explain <query> tell you?  Have you analyzed the database?
>
>
> This is the QUERY PLAN
> Hash Left Join  (cost=25.00..412868.31 rows=4979686 width=17)
>   Hash Cond: (("outer".groupnum = "inner".groupnum) AND
> (("outer".sku)::text = ("inner".sku)::text))
>   Filter: (("inner".url IS NULL) OR (("inner".url)::text = ''::text))
>   ->  Seq Scan on prdt_old mc  (cost=0.00..288349.86 rows=4979686 width=17)
>   ->  Hash  (cost=20.00..20.00 rows=1000 width=78)
>         ->  Seq Scan on prdt_new mi  (cost=0.00..20.00 rows=1000 width=78)
>
>
> > What are your postgresql.conf settings?
>
> What suspected specific setting need to be changed?
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

Attachment

pgsql-general by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Referential integrity using constant in foreign key
Next
From: Yudie Pg
Date:
Subject: Re: Table partition for very large table