Re: Slow Query- Simple taking - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: Slow Query- Simple taking
Date
Msg-id 4CBDC0420200002500036B64@gw.wicourts.gov
Whole thread Raw
In response to Slow Query- Simple taking  ("Ozer, Pam" <pozer@automotive.com>)
Responses Re: Slow Query- Simple taking
List pgsql-performance
"Ozer, Pam" <pozer@automotive.com> wrote:

> I have the following query running on 8.4, which takes 3516 ms.
> It is very straight forward.  It brings back 116412 records.  The
> explain only takes 1348ms

The EXPLAIN ANALYZE doesn't have to return 116412 rows to the
client.  It doesn't seem too out of line to me that it takes two
seconds to do that.

> Can someone tell me why after it runs the index scan it hen runs a
> bitmap heap scan?

Without visiting the heap it can't tell whether the tuples it has
found are visible to your query.  Also, it needs to get the actual
values out of the heap.

> It should not take this long to run should it?

If you want an answer to that, we need more information.  See this
page for ideas:

http://wiki.postgresql.org/wiki/SlowQueryQuestions

> If I limit the results it comes back in 300ms.

I don't find that surprising.  Wouldn't you think that reading and
transmitting more rows would take more time?

-Kevin

pgsql-performance by date:

Previous
From: "Ozer, Pam"
Date:
Subject: Slow Query- Simple taking
Next
From: Mathieu De Zutter
Date:
Subject: Re: Slow Query- Simple taking