Re: Need indexes on empty tables for good performance ?

Lenard, Rohan (Rohan) wrote:

> I've read that indexes aren't used for COUNT(*) and I've noticed
> (7.3.x) with EXPLAIN that indexes never seem to be used on empty
> tables - is there any reason to have indexes on empty tables, or will
> postgresql never use them.

You could add a row, vacuum analyze, delete the row, etc.... Then you
are fine until you vacuum analyze again ;-)

This is a feature designed to prevent really bad plans when you are
loading tables with data. However, you are right. It can create bad
plans sometimes.

Any chance one can eventually come up with a way to tell the planner
that an empty table is expected not to grow? Otherwise, I can see
nightmares in a data warehouse environment where you have an empty
parent table...

Best Wishes,
Chris Travers
Metatron Technology Consulting