On Mon, 24 Jun 2002 08:43:16 -0700 (PDT)
"Mike Harding" <mvh(at)ix(dot)netcom(dot)com> wrote:
> Why is a sequential scan be done for MAX of an indexed column? This
> is obviously pretty painful for large tables...
This is an FAQ -- check the archives for much more discussion of it.
In short, the workaround is to create a btree index on the column
in question, and do:
SELECT num FROM boogers ORDER BY num LIMIT 1;
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC