From: frbn@efbs-seafrigo.fr
To: Tom Lane <tgl@sss.pgh.pa.us>
To: sszabo@megazone23.bigpanda.com
Cc: pgsql-sql@postgresql.org
Subject: Re: SELECT * FROM t where p or q;
Date: Tue, 20 Nov 2001 18:42:05 +0100
Message-ID: <3BFA95ED.EE814258@efbs-seafrigo.fr> (raw)
References: <3BF51764.8BEAC873@efbs-seafrigo.fr>
<29635.1006270833@sss.pgh.pa.us>
thanks a lot to pay attention to my problem
thanks to you, after a 15mn long "vacuum ANALYZE table" :(
the "OR" works now just how it was supposed to.
I wrongly thought that a "vacuum" did a "vacuum ANALYZE" by default.
I can't figure out how Tera-bytes databases admins can
deal with such vacuum delays!
(except if a vacuum is only needed every 10 millions records :] )
Best regards,
Franck.
Tom Lane wrote :
>
> frbn@efbs-seafrigo.fr writes:
> > on a +10 millions rec table, a simple select:
> > SELECT * FROM tab where num = x;
> > time: 5 secondes
>
> > SELECT * FROM tab WHERE num = x OR num = y;
> > time: more than 10 mn !!!
>
> What does EXPLAIN show? Have you VACUUM ANALYZEd the table recently
> (or indeed ever)? This looks a lot like the behavior on a
> never-vacuumed table --- the default statistical assumptions are such
> that an indexscan looks like a win for one equality clause, but not
> for two ORed clauses.
>
> regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: frbn@efbs-seafrigo.fr, tgl@sss.pgh.pa.us, sszabo@megazone23.bigpanda.com
Subject: Re: SELECT * FROM t where p or q;
In-Reply-To: <3BFA95ED.EE814258@efbs-seafrigo.fr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox