public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jussi Mikkola <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: scott.marlowe <[email protected]>
Cc: 'PostgreSQL General' <[email protected]>
Cc: Postgresql Advocacy <[email protected]>
Subject: Re: New PostgreSQL search resource
Date: Mon, 19 Jan 2004 21:33:59 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

I think most of the people use http://www.postgresql.org/search.cgi

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.
>>  
>>
>
>

view thread (14+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: New PostgreSQL search resource
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox