Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE - Mailing list pgsql-performance

From Tom Lane
Subject Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE
Date
Msg-id 12378.1045267912@sss.pgh.pa.us
Whole thread Raw
In response to Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE  (SLetovsky@aol.com)
Responses Re: [Gmod-schema] Re: performace problem after VACUUM  (Scott Cain <cain@cshl.org>)
List pgsql-performance
SLetovsky@aol.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

pgsql-performance by date:

Previous
From: SLetovsky@aol.com
Date:
Subject: Re: [Gmod-schema] Re: performace problem after VACUUM ANALYZE
Next
From: Curt Sampson
Date:
Subject: Re: [HACKERS] WAL replay logic (was Re: Mount options for