| From: | Matheus de Oliveira <matioli(dot)matheus(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 13:56:47 |
| Message-ID: | CAJghg4Jd285HNma1tqFB26iJQw+GBug4VgnopA1E=YY4OMOWQw@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
>
Could you try chaning your query and sending the EXPLAIN of the following?
Instead of `node_id in ('175769', '175771', ...)` try `node_in IN
(VALUES('175769'), ('175771'), ... )`.
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2014-06-26 14:05:35 | Re: how to improve perf of 131MM row table? |
| Previous Message | AJ Weber | 2014-06-26 13:26:06 | Re: how to improve perf of 131MM row table? |