AW: SourceForge & Postgres

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'mlw'" <markw(at)mohawksoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: SourceForge & Postgres
Date: 2000-12-13 10:17:43
Message-ID: 11C1E6749A55D411A9670001FA687963368179@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > anyway? ;-)) If so, a search for artistid 100050450 definitely *should*
> > use a sequential scan.
>
> I tested this statement against the database and you are right, about 14
> seconds with the index, 4 without.

Now I don't understand the problem any more. Are you complaining, that
the optimizer is choosing a faster path ? Or are you saying, that you also
get the seq scan for other very infrequent values ?

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2000-12-13 10:58:25 Re: Bug in ILIKE function?
Previous Message Fabio Nanni 2000-12-13 09:35:57 triggers and actions tree/2