From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Jussi Mikkola <jussi(dot)mikkola(at)bonware(dot)com> |
Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, "'PostgreSQL General'" <pgsql-general(at)postgresql(dot)org>, Postgresql Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: New PostgreSQL search resource |
Date: | 2004-01-19 19:42:15 |
Message-ID: | 400C3317.6010504@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general pgsql-www |
Jussi Mikkola wrote:
> I think most of the people use http://www.postgresql.org/search.cgi
Yep... Supposedly it is being worked on to make it faster.
J
>
> Default settings, search for select distinct returns in about 10
> minutes, with "You haven't typed any word(s) to search for."
>
> Same query with match full phrase... (I did not wait long enough. But
> several minutes in any case. Don't know about the result.)
>
> Same query with match full phrase and 7.4 documentation. 2 results in
> 5 seconds. Results are select into and pg_select.
>
> Could we do something to this search? (Change the defaults, divide it
> to smaller parts, use different search engine...)
>
> Rgs,
>
> Jussi
>
>
>
>
>
> Joshua D. Drake wrote:
>
>>
>>> Not really. with htdig, I can do "select distinct" on the 7.3 docs
>>> and I get exactly 7 responses back, and they all have select
>>> followed immediately by distinct, with only space, CR / LF etc in
>>> between.
>>>
>>>
>>>
>> Well, if you search for select distinct... OpenFTS automatically
>> searches
>> for select & distinct. My search returned:
>>
>> 5 results with the first one being this:
>>
>> http://www.commandprompt.com/community//search.lxp?lxpwrap=734/queries-select-lists.html
>>
>>
>> Which seems fairly accurate ;). Perhaps a better description of what
>> the problem actually is or
>> the behavior you are expecting?
>>
>> SIncerely,
>>
>> Joshua D. Drake
>>
>>
>>
>>> And the & symbol josh recommended shows as being ignored, so that
>>> didn't work either.
>>>
>>> Word combos like "bulk loads" or "run-time configuration" are quite
>>> handy filters.
>>>
>>>
>>
>>
>
>
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-01-19 20:27:13 | Re: New PostgreSQL search resource |
Previous Message | Jussi Mikkola | 2004-01-19 19:33:59 | Re: New PostgreSQL search resource |
From | Date | Subject | |
---|---|---|---|
Next Message | Jack Orenstein | 2004-01-19 19:45:27 | Re: Detecting database corruption |
Previous Message | Stephan Szabo | 2004-01-19 19:36:46 | Re: Precedence of a TRIGGER vs. a CHECK on a column |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2004-01-19 19:55:29 | Re: Bricolage: Impressive |
Previous Message | Jussi Mikkola | 2004-01-19 19:33:59 | Re: New PostgreSQL search resource |