Re: Problem with LIKE-Performance - Mailing list pgsql-performance

From Tarabas (Manuel Rorarius)
Subject Re: Problem with LIKE-Performance
Date
Msg-id 653249740.20060418173459@tarabas.de
Whole thread Raw
In response to Re: Problem with LIKE-Performance  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with LIKE-Performance  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Hi Tom,

TL> "Tarabas (Manuel Rorarius)" <tarabas@tarabas.de> writes:
>> I get the following explain and I am troubled by the very high
>> "startup_cost" ... does anyone have any idea why that value is so
>> high?

>> {SEQSCAN
>>    :startup_cost 100000000.00

TL> You have enable_seqscan = off, no?

You were right, I was testing this and had it removed, but somehow I
must have hit the wrong button in pgadmin and it was not successfully
removed from the database.

After removing the enable_seqscan = off and making sure it was gone,
it is a lot faster again.

Now it takes about 469.841 ms for the select.

TL> Please refrain from posting EXPLAIN VERBOSE unless it's specifically
TL> requested ...

mea culpa, i will not do that again :-)

Best regards
Manuel


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: SELECT FOR UPDATE performance is bad
Next
From: "Hakan Kocaman"
Date:
Subject: Re: Problem with LIKE-Performance