Skip site navigation (1) Skip section navigation (2)

Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: SLetovsky(at)aol(dot)com
Cc: cain(at)cshl(dot)org, pgsql-performance(at)postgresql(dot)org,gmod-schema(at)lists(dot)sourceforge(dot)net
Subject: Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE
Date: 2003-02-15 00:11:52
Message-ID: 12378.1045267912@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
SLetovsky(at)aol(dot)com writes:
> Am I correct in interpreting your comments as saying you believe that
> if we could lose the OR and the strand constraint PG would probably
> use the index properly?

No, I said I thought it could do it without that ;-).  But yes, you'd
have a much less fragile query if you could lose the OR condition.

Have you looked into using a UNION ALL instead of OR to merge the two
sets of results?  It sounds grotty, but might be faster...

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Curt SampsonDate: 2003-02-15 08:29:21
Subject: Re: [HACKERS] WAL replay logic (was Re: Mount options for
Previous:From: Tom LaneDate: 2003-02-14 23:19:17
Subject: Re: performace problem after VACUUM ANALYZE

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group