Found answer somewhere on PostgreSQL web site: optimizer uses sequentialscan anyway if the number of records are small.
-- Michael