Re: [PERFORM] Troubleshooting query performance issues - resolved (sort of)

2013-09-27 Thread Jim Garrison
We have traced this to the *addition* of a two-column index. > -Original Message- > From: pgsql-performance-ow...@postgresql.org [mailto:pgsql- > performance-ow...@postgresql.org] On Behalf Of Jim Garrison > Sent: Wednesday, September 25, 2013 8:58 AM > To: pg

Re: [PERFORM] Troubleshooting query performance issues - Resolved (sort of)

2013-09-27 Thread Jim Garrison
.@postgresql.org [mailto:pgsql- > performance-ow...@postgresql.org] On Behalf Of Jim Garrison > Sent: Wednesday, September 25, 2013 8:58 AM > To: pgsql-performance@postgresql.org > Subject: [PERFORM] Troubleshooting query performance issues > > I spent about a week optimizing a query in our

[PERFORM] Troubleshooting query performance issues

2013-09-25 Thread Jim Garrison
I spent about a week optimizing a query in our performance-testing environment, which has hardware similar to production. I was able to refactor the query and reduce the runtime from hours to about 40 seconds, through the use of CTEs and a couple of new indexes. The database was rebuilt and ref