Rajesh,
> I want my query to use indexes for company name searches but its not
> happening unless
> is use '=' which does not server the purpose.
>
> eg
>
> tradein_clients=# explain SELECT co_name FROM unified_data where
> co_name ilike '%rajesh%' ;
Well, for an *anchored* case-insensitive
I need to do an UPDATE on a large (100 million record) table. Is there
any way to speed up the process (Like turning off the transaction log)?
So far postgres has been handling the large database exceptionally well
(large \copy imports and WHERE clauses w/ multiple params) but it is
killing me o
Thanks Josh
I normally use tsearch for full text search i will probably use that
or may be this what u suggested.
regds
mallah.
> Rajesh,
>
>> I want my query to use indexes for company name searches but its not happening
>unless
>> is use '=' which does not server the purpose.
>>
>> eg
>>
>
Hi,
I must be doing something silly. I have a 900MHz, 384MB RAM, and
this thing is slow. (Postgresql-7.1.2).
And growing exponencially slower.
SQL: http://John.Vicherek.com/slow/schema.sql (save to /tmp/schema.sql)
am.dat: http://John.Vicherek.com/slow/am.dat (save to /tmp/am.dat )
pe
and I forgot to mention that my stats are available at:
http://John.Vicherek.com/slow/times.query.txt
John
On Sun, 11 Aug 2002 [EMAIL PROTECTED] wrote:
>
>
> Hi,
>
> I must be doing something silly. I have a 900MHz, 384MB RAM, and
> this thing is slow. (Postgresql-7.1.2).
>
> And