Re: Postgres not using indexes - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: Postgres not using indexes
Date
Msg-id 4D9322E8020000250003BF8C@gw.wicourts.gov
Whole thread Raw
In response to Re: Postgres not using indexes  (Lawrence Cohan <LCohan@web.com>)
Responses Re: Postgres not using indexes  (Lawrence Cohan <LCohan@web.com>)
Re: Postgres not using indexes  (Lawrence Cohan <LCohan@web.com>)
List pgsql-bugs
Lawrence Cohan <LCohan@web.com> wrote:
> From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]

>> [configuration advice]

>> If, after reading the above-cited page and tuning your server you
>> still have performance problems, pick one query to work on first,
>> and follow the step outlined here:
>>
>> http://wiki.postgresql.org/wiki/SlowQueryQuestions

> We thank you for the links that have a lots of info and please
> note that we tuned our servers as recommended by Enterprise DB
> experts while they were in house for our hardware/software
> migrations and the setting you mentioned are in place already.

Then the next step would be to provide enough information on one of
the slow queries for people to be able to offer useful advice.  Your
other post showed the query and the EXPLAIN ANALYZE output, but the
other information listed in the above-cited page is useful when
trying to understand a problem.  I'm particularly curious about the
data types of the id columns and the specifics of the index
definitions.

-Kevin

pgsql-bugs by date:

Previous
From: julia.jacobson@arcor.de
Date:
Subject: Re: BUG #5960: No rule to make target 'libpq.a', needed by 'all-static-lib'
Next
From: Jon Nelson
Date:
Subject: backend for database 'A' crashes/is killed -> corrupt index in database 'B'