public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marc G. Fournier <[email protected]>
To: Josh Berkus <[email protected]>
Cc: John Hansen <[email protected]>
Cc: Oleg Bartunov <[email protected]>
Cc: PostgreSQL WWW Mailing List <[email protected]>
Subject: Re: Suggestion for improving Archives
Date: Sat, 4 Sep 2004 16:10:16 -0300 (ADT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Sat, 4 Sep 2004, Josh Berkus wrote:
> Guys,
>
>> However, only one of those resources, pgsql.ru, could be made to make
>> available new threads on an hourly basis, or maybe even realtime.
>>
>> Either way, I'm not fuzzed, whichever works the best.
>
> Hmmmm .....
>
> ===========================
> Click to Search the Archives:
>
> -- PGSQL.ru's Full Text Search of Archives using OpenFTS (fast, all PostgreSQL
> sites)
>
> -- Google Groups (fast, general search of Usenet and PostgreSQL mailing lists)
>
> -- Monharc Archive Search (slow but includes up-to-the-last-hour posts)
When is the last time you used the search on archives.postgresql.org? The
following was searching mvcc:
"Documents 1-10 of total 1576 found. Searching in 390035 documents took
0.037 seconds."
the following was searching 'wal vadim':
"Documents 1-10 of total 880 found. Searching in 390035 documents took
0.441 seconds."
the following was searching "postgresql releases 8.0":
"Documents 1-10 of total 2190 found. Searching in 390035 documents took
1.882 seconds."
the followign was searching "nested transaction support":
"Documents 1-10 of total 383 found. Searching in 390035 documents took
4.714 seconds."
Not what I'd consider "slow" ... granted, that last one on Google too .2
seconds, but when we can build a server farm like them, then I'll be
worried about 4secs vs .2 :)
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [email protected] Yahoo!: yscrappy ICQ: 7615664
view thread (23+ 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]
Subject: Re: Suggestion for improving Archives
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