| From: | Yudie Gunawan <yudiepg(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Table partition for very large table |
| Date: | 2005-03-28 19:50:06 |
| Message-ID: | e460d0c050328115032b743f9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-03-28 20:18:23 | Re: Table partition for very large table |
| Previous Message | Guy Rouillier | 2005-03-28 19:43:03 | Re: Debugging deadlocks |