From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Mnogosearch (Was: Re: website doc search is ... ) |
Date: | 2004-01-01 18:52:42 |
Message-ID: | 20040101145147.C913@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 1 Jan 2004, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > 186_archives=# \d ndict7
> > Table "public.ndict7"
> > Column | Type | Modifiers
> > ---------+---------+--------------------
> > url_id | integer | not null default 0
> > word_id | integer | not null default 0
> > intag | integer | not null default 0
> > Indexes:
> > "n7_url" btree (url_id)
> > "n7_word" btree (word_id)
> >
> >
> > The slowdown is the LIKE condition, as the ndict[78] word_id conditions
> > return near instantly when run individually, and when I run the 'url/LIKE'
> > condition, it takes "forever" ...
>
> Does it help to CLUSTER url.url? Is your data being loaded in so
> identical values used by LIKE are next to each other?
I'm loading up a MySQL 4.1 database right now, along side of a PgSQL 7.4
one WITHOUT OIDs ... should take several days to fully load, but it will
be interesting to compare them all ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2004-01-01 19:00:28 | Re: Mnogosearch (Was: Re: website doc search is ... ) |
Previous Message | Peter Eisentraut | 2004-01-01 18:21:49 | Re: 'like' refuses to use an index??? |