"Bruce Momjian" <bruce(at)momjian(dot)us> writes:
> Magnus Hagander wrote:
>> We are sucking a lot of this data down to the db on
>> search.postgresql.org already. Does it make sense to do it there
>> perhaps? Is there need for anything more than a unique-messageid-hit? If
>> that's all we need, we could easily have an url like
>> http://search.postgresql.org/search?msgid=19873987123(at)foo(dot)com redirect
>> to the proper page on archives?
> Agreed, we just need search to index the message-id line and we can link
> to that easily.
I would very much like such a URL as well. At a guess it would require hacking
the tsearch parser we use for the search engine on the web site?
Ask me about EnterpriseDB's Slony Replication support!
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-03-17 16:48:16|
|Subject: Re: Better error message for select_common_type() |
|Previous:||From: Tom Lane||Date: 2008-03-17 16:23:06|
|Subject: Re: [PATCHES] CIC and deadlocks |