Re: Left Join Not Using Index?

Basically this query searches those two tables, which model a message board,
for text strings...

I'll have to take a closer look and see.

> From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
> Date: Wed, 23 Apr 2003 14:00:42 +0800
> To: Hunter Hillegas <lists(at)lastonepicked(dot)com>
> Cc: PostgreSQL <pgsql-general(at)postgresql(dot)org>
> Subject: Re: [GENERAL] Left Join Not Using Index?
>
> I think he said you have to change your query or your database layout to
> get better speed.
>
> Can you think of a different query or set of queries that will do what you
> want?
>
> What are you trying to achieve with your query?
>
> Link.
>
> At 10:35 PM 4/22/2003 -0700, Hunter Hillegas wrote:
>
>> So, what you're basically saying is that my best bet for improving the speed
>> of a query to get this result set is to tweak my settings and get faster
>> hardware?
>>
>>> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>>> Date: Wed, 23 Apr 2003 01:30:05 -0400
>>> To: Hunter Hillegas <lists(at)lastonepicked(dot)com>
>>> Cc: Dann Corbit <DCorbit(at)connx(dot)com>, Stephan Szabo
>>> <sszabo(at)megazone23(dot)bigpanda(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org>
>>> Subject: Re: [GENERAL] Left Join Not Using Index?
>>>
>>> Hunter Hillegas <lists(at)lastonepicked(dot)com> writes:
>>>> Can anyone point me in another direction to optimize this
>>>
>>> AFAICS you cannot improve that without changing the query structure
>>> and/or the database layout. Because the WHERE clause is a bunch of OR'd
>>> conditions, it's useless for restricting either individual table scan
>>> making up the join --- there is really no implementation short of
>
>