| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commit fest? |
| Date: | 2008-03-17 16:31:32 |
| Message-ID: | 87y78hb9cr.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"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?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-17 16:48:16 | Re: Better error message for select_common_type() |
| Previous Message | Tom Lane | 2008-03-17 16:23:06 | Re: [PATCHES] CIC and deadlocks |