On Tue, May 21, 2013 at 3:54 PM, <fburgess@radiantblue.com> wrote:
> The SARS_ACTS table currently has 37,115,515 rows
>
> we have indexed: idx_sars_acts_acts_run_id ON SARS_ACTS USING btree
> (sars_run_id)
> we have pk constraint on the SARS_ACTS_RUN table; sars_acts_run_pkey PRIM=
ARY
> KEY (id )
>
> serverdb=3D# explain select count(*) as y0_ from SARS_ACTS this_ inner jo=
in
> SARS_ACTS_RUN tr1_ on this_.SARS_RUN_ID=3Dtr1_.ID where tr1_.ALGORITHM=3D=
'SMAT';
This is not a bug, you should write to the
pgsql-general@postgresql.org or pgsql-performance@postgresql.org
mailing lists.
anyway, seems that you need an additional index on SARS_ACTS_RUN.ALGORITHM
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitaci=F3n
Phone: +593 4 5107566 Cell: +593 987171157