Skip site navigation (1) Skip section navigation (2)

Re: New PostgreSQL search resource

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 (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-generalpgsql-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


In response to

pgsql-www by date

Next:From: Dave PageDate: 2004-01-19 19:55:29
Subject: Re: Bricolage: Impressive
Previous:From: Jussi MikkolaDate: 2004-01-19 19:33:59
Subject: Re: New PostgreSQL search resource

pgsql-advocacy by date

Next:From: scott.marloweDate: 2004-01-19 20:27:13
Subject: Re: New PostgreSQL search resource
Previous:From: Jussi MikkolaDate: 2004-01-19 19:33:59
Subject: Re: New PostgreSQL search resource

pgsql-general by date

Next:From: Jack OrensteinDate: 2004-01-19 19:45:27
Subject: Re: Detecting database corruption
Previous:From: Stephan SzaboDate: 2004-01-19 19:36:46
Subject: Re: Precedence of a TRIGGER vs. a CHECK on a column

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group