Andy wrote:
Hi,
I have a table with varchar and text columns, and I have to search
through these text in the whole table.
An example would be:
SELECT * FROM table
WHERE name like '%john%' or street like '%srt%'
Anyway, the query planner always does seq scan on
>
for great tips from Yahoo! Answers
<http://answers.yahoo.com/dir/index;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx?link=ask&sid=396546091>
users. !DSPAM:5,45beea6d287779832115503!
--
Rigmor Ukuhe
Finestmedia Ltd | Software Dev
Play with vacuum_cost_delay option. In our case it made BIG difference
(going from very heavy hitting to almost unnoticed vacuuming.)
Hope it helps.
Rigmor Ukuhe
>
> If we run vacuum less frequently, degradation
> continues to the point that we can't keep up with the
> throughput,
(int_value = 0)
> Total runtime: 13560.862 ms
Is your int_value data type int4? If not then use "... from job_property
where int_value = '0'"
Indexes are used only if datatypes matches.
Rigmor Ukuhe
>
>
>
> Is this more or less normal or can we optimize this a
i
would give it a try in case of that kind of requirements.
Rigmor Ukuhe
> Then I decided to see what happens with 20 clients.
>
> MySQL clocked in at 650 seconds. During this time the machine was VERY
> unresponsive. To be fair, that could be Linux, not MySQL.
>
> PG (7.3.4)
Hi,
I have many indexes somehow overlaping like:
... btree ("STATUS", "VISIBLE", "NP_ID");
... btree ("STATUS", "VISIBLE");
is perfomance gained by "more exact" index worth overhead with managing
indexes.
Rigmor Ukuhe
Finestmedia L
e comes?
There are about 37K rows and only about 100 of then are not "NP_ID" = 0
For a workaround i use WHERE "NP_ID" >= '1' and if works as speedy as '> 1'
Rigmor Ukuhe
---
Outgoing mail is certified Virus Free.
Checked b
> > What causes this behaviour? is there any workaround? Suggestions?
> >
>
> How many rows are there in the table, and can you post the
> 'explain analyze' for both queries after doing a 'vacuum verbose analyze
> [tablename]'?
There are about 2500 rows in that table.
1st query explain analyze: S
_STATISTICS_reo_id,
PRIORITY_STATISTICS_reo_id, PRIORITY_STATISTICS_reo_id,
PRIORITY_STATISTICS_reo_id, PRIORITY_STATISTICS_reo_id,
PRIORITY_STATISTICS_reo_id, PRIORITY_STATISTICS_reo_id,
PRIORITY_STATISTICS_reo_id, PRIORITY_STATISTICS_reo_id,
PRIORITY_STATISTICS_reo_id, PRIORITY_STATISTICS_reo_id,
PRIORITY_STATISTI
