Hi, meanwhile I have received the hint to make postgres use the index via
SET ENABLE_SEQSCAN=FALSE; which fits perfectly. The execution plan now indicates full use of index. Nevertheless this is merely a workaround. Maybe the io-costs are configured to cheap. thanks :-) -----Ursprüngliche Nachricht----- Von: Richard Huxton [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. Oktober 2005 12:22 An: Nörder-Tuitje, Marcus Cc: pgsql-performance@postgresql.org Betreff: Re: [PERFORM] Optimizer misconfigured ? Nörder-Tuitje wrote: > > Hello, > > I have a strange effect on upcoming structure : People will be wanting the output of EXPLAIN ANALYSE on that query. They'll also ask whether you've VACUUMed, ANALYSEd and configured your postgresql.conf correctly. -- Richard Huxton Archonet Ltd ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
