Re: Suggestion for improving Archives - Mailing list pgsql-www

From Dave Page
Subject Re: Suggestion for improving Archives
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E407B3F3@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Suggestion for improving Archives  (Josh Berkus <josh@agliodbs.com>)
List pgsql-www


-----Original Message-----
From: pgsql-www-owner@postgresql.org on behalf of Greg Sabino Mullane
Sent: Sat 9/4/2004 8:57 PM
To: pgsql-www@postgresql.org
Subject: Re: [pgsql-www] Suggestion for improving Archives
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
 
> the followign was searching "nested transaction support":
>
> "Documents 1-10 of total 383 found. Searching in 390035 documents took
> 4.714 seconds."
 
> The self-reported time should really not be used. I just ran a query, for
> example, that took 8 seconds as measured by my local clock, but reported
> searching in under 2 seconds: so obviously there are some other factors
> here. (I'll give maybe half a second for network times on my end).

Factors that would apply equally if we used pgsql.ru - what you are most likely seeing it the ads and other graphics
loading.If we used pgsql.ru, you would still have those coming from hub.org.
 
 
> pgsql.ru: very fast, searches all sites at once, no advertisements,
> nice "group by site" feature, cool Mozilla plugin, BSD-licensed tech,
> written by PG developers

Would be linked from main site with ads if we started using it 'officially'.

> search.postgresql.org: linked from main site?

Yes, should we leave it hidden? :-) Note that in comparison to pgsql.ru, search.pg.org also groups by site, searches
allsites at once and is seriously hacked by PG developers (not written I grant you). It is also open source (GPL, not
BSD- not that I think that is particularly important to any of the users).
 
 
Regards, Dave.

pgsql-www by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: Suggestion for improving Archives
Next
From: Robert Treat
Date:
Subject: Re: Comment forms in interactive docs