| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | AJ Weber <aweber(at)comcast(dot)net> |
| Cc: | Shaun Thomas <sthomas(at)optionshouse(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: how to improve perf of 131MM row table? |
| Date: | 2014-06-26 15:35:00 |
| Message-ID: | CAGTBQpZNueaUF8=ZZRZW+v4o5Vfdg0ssJdqgT_sMnH7R0JfqZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 26, 2014 at 10:26 AM, AJ Weber <aweber(at)comcast(dot)net> wrote:
> OK, the sample query is attached (hopefully attachments are allowed) as
> "query.sql".
> The "master table" definition is attached as "table1.sql".
> The "detail table" definition is attached as "table2.sql".
> The EXPLAIN (ANALYZE, BUFFERS) output is here:
> http://explain.depesz.com/s/vd5
I think the problem is that you're sending strings in the ids, instead
of integers.
Remove the quotes, leave only the numbers. That will make pg able to
infer that node.id = prop.node_id means it can also use an index on
alf_node_properties.
I think.
Try.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AJ Weber | 2014-06-26 15:38:53 | Re: how to improve perf of 131MM row table? |
| Previous Message | AJ Weber | 2014-06-26 14:50:15 | Re: how to improve perf of 131MM row table? |