On Thu, Oct 28, 2010 at 10:39 AM, Robert Haas <robertmh...@gmail.com> wrote: >> Can someone tell me why after it runs the index scan it hen runs a bitmap >> heap scan? It should not take this long to run should it? If I limit the >> results it comes back in 300ms. > > It doesn't. The EXPLAIN output shows it running the bitmap index scan > first and then bitmap heap scan. The bitmap index scan is taking 22 > ms, and the bitmap index and bitmap heap scans combined are taking 402 > ms. The sort is then taking another 800+ ms for a total of 1325 ms. > Any additional time is spent returning rows to the client.
Doh! I misread your email. You had it right, and I'm all wet. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
