Re: how to improve perf of 131MM row table? - Mailing list pgsql-performance

From Claudio Freire
Subject Re: how to improve perf of 131MM row table?
Date
Msg-id CAGTBQpZNueaUF8=ZZRZW+v4o5Vfdg0ssJdqgT_sMnH7R0JfqZg@mail.gmail.com
Whole thread Raw
In response to Re: how to improve perf of 131MM row table?  (AJ Weber <aweber@comcast.net>)
Responses Re: how to improve perf of 131MM row table?
List pgsql-performance
On Thu, Jun 26, 2014 at 10:26 AM, AJ Weber <aweber@comcast.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.


pgsql-performance by date:

Previous
From: AJ Weber
Date:
Subject: Re: how to improve perf of 131MM row table?
Next
From: AJ Weber
Date:
Subject: Re: how to improve perf of 131MM row table?