Re: Commit fest?

bruce wrote:
> > Yea, that is a big problem because the URLs are dynamic. I have the
> > comments based on message id but there is no way to hook that to a URL.
>
> I have modified the code so each email message now shows a _permanent_
> URL at the top, e.g.
>
> Permanent URL: http://momjian.us/mhonarc/patches/44DA31B1.3090700.enterprisedb.com.html

I have shortened the URL using md5:

Permanent URL: http://momjian.us/mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html

So _now_ it is permanent. ;-)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> bruce wrote:
>> > Yea, that is a big problem because the URLs are dynamic. I have the
>> > comments based on message id but there is no way to hook that to a URL.
>>
>> I have modified the code so each email message now shows a _permanent_
>> URL at the top, e.g.
>>
>> Permanent URL: http://momjian.us/mhonarc/patches/44DA31B1.3090700.enterprisedb.com.html
>
> I have shortened the URL using md5:
>
> Permanent URL: http://momjian.us/mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html
>
> So _now_ it is permanent. ;-)

Not Found
The requested URL /mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html was not found on this server.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning

Gregory Stark wrote:
> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>
> > bruce wrote:
> >> > Yea, that is a big problem because the URLs are dynamic. I have the
> >> > comments based on message id but there is no way to hook that to a URL.
> >>
> >> I have modified the code so each email message now shows a _permanent_
> >> URL at the top, e.g.
> >>
> >> Permanent URL: http://momjian.us/mhonarc/patches/44DA31B1.3090700.enterprisedb.com.html
> >
> > I have shortened the URL using md5:
> >
> > Permanent URL: http://momjian.us/mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html
> >
> > So _now_ it is permanent. ;-)
>
> Not Found
> The requested URL /mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html was not found on this server.

Yes, sorry, I had to remove the feature. I will re-add it
tomorrow/Sunday.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> Gregory Stark wrote:
>> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>>
>> > bruce wrote:
>> >> > Yea, that is a big problem because the URLs are dynamic. I have the
>> >> > comments based on message id but there is no way to hook that to a URL.
>> >>
>> >> I have modified the code so each email message now shows a _permanent_
>> >> URL at the top, e.g.
>> >>
>> >> Permanent URL: http://momjian.us/mhonarc/patches/44DA31B1.3090700.enterprisedb.com.html
>> >
>> > I have shortened the URL using md5:
>> >
>> > Permanent URL: http://momjian.us/mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html
>> >
>> > So _now_ it is permanent. ;-)
>>
>> Not Found
>> The requested URL /mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html was not found on this server.
>
> Yes, sorry, I had to remove the feature. I will re-add it
> tomorrow/Sunday.

Actually, is it just me or has the whole patch queue disappeared?
Everything under /mhonarc/patches seems to be gone.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 15 Mar 2008 17:05:44 +0000
Gregory Stark <stark(at)enterprisedb(dot)com> wrote:

> > Yes, sorry, I had to remove the feature. I will re-add it
> > tomorrow/Sunday.
>
> Actually, is it just me or has the whole patch queue disappeared?
> Everything under /mhonarc/patches seems to be gone.

Yep, she's gone.

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL political pundit | Mocker of Dolphins

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH3AeoATb/zqfZUUQRAmyPAJ423Oxx3BRQY4Jxsug+hPCz83ONcgCfQ5ha
Uhmyg/YQK/JXQAH/L8z63vM=
=bbxD
-----END PGP SIGNATURE-----

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Actually, is it just me or has the whole patch queue disappeared?
> Everything under /mhonarc/patches seems to be gone.

/mhonarc? The URL I've always used is
http://momjian.us/cgi-bin/pgpatches

regards, tom lane

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> Actually, is it just me or has the whole patch queue disappeared?
>> Everything under /mhonarc/patches seems to be gone.
>
> /mhonarc? The URL I've always used is
> http://momjian.us/cgi-bin/pgpatches

Yeah, but note that all the links in that page including the Next Page go to
/mhonarc. In any case Bruce seems to have regenerated the files.

I'm curious where the comments are being stored, since it's not in the html
source. The javascript must be pulling them from another url?

Also, I think I would prefer you *not* md5sum the message-id. The message-id
is globally unique. Given a message-id we have at least a fighting chance of
finding it in our local mail spool or the Postgres mail archive. (Though the
Postgres search engine doesn't support that currently).

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!

Gregory Stark wrote:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> >> Actually, is it just me or has the whole patch queue disappeared?
> >> Everything under /mhonarc/patches seems to be gone.
> >
> > /mhonarc? The URL I've always used is
> > http://momjian.us/cgi-bin/pgpatches
>
> Yeah, but note that all the links in that page including the Next Page go to
> /mhonarc. In any case Bruce seems to have regenerated the files.

Good, should be online now with permanent links too.

> I'm curious where the comments are being stored, since it's not in the html
> source. The javascript must be pulling them from another url?

The comments are stored at JS-Kit:

http://js-kit.com/comments/

> Also, I think I would prefer you *not* md5sum the message-id. The message-id
> is globally unique. Given a message-id we have at least a fighting chance of
> finding it in our local mail spool or the Postgres mail archive. (Though the
> Postgres search engine doesn't support that currently).

Well, I can't have "@" in the URL because it is usually forbidden by
browsers for phishing protection, so I was converting @ to '.' anyway.
What I have now done is display the real message id and MD5 permanent
link at the top of each message, e.g.:

http://momjian.us/mhonarc/patches/msg00054.html

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

>> I'm curious where the comments are being stored, since it's not in the html
>> source. The javascript must be pulling them from another url?
>
> The comments are stored at JS-Kit:
>
> http://js-kit.com/comments/

It's stored in their server?

>
> Well, I can't have "@" in the URL because it is usually forbidden by
> browsers for phishing protection, so I was converting @ to '.' anyway.
> What I have now done is display the real message id and MD5 permanent
> link at the top of each message, e.g.:
>
> http://momjian.us/mhonarc/patches/msg00054.html

Any chance we could put that on the actual listing page somehow. perhaps in a
tiny font?? I want to be able to copy the thread and get enough information
for future reference.

Also, any chance you could use the permanent urls in the thread listing?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!

Gregory Stark wrote:
> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>
> >> I'm curious where the comments are being stored, since it's not in the html
> >> source. The javascript must be pulling them from another url?
> >
> > The comments are stored at JS-Kit:
> >
> > http://js-kit.com/comments/
>
> It's stored in their server?

Yes, that was the beauty of it --- I just add javascript with a tag and
all comments are handled by them.

> > Well, I can't have "@" in the URL because it is usually forbidden by
> > browsers for phishing protection, so I was converting @ to '.' anyway.
> > What I have now done is display the real message id and MD5 permanent
> > link at the top of each message, e.g.:
> >
> > http://momjian.us/mhonarc/patches/msg00054.html
>
> Any chance we could put that on the actual listing page somehow. perhaps in a
> tiny font?? I want to be able to copy the thread and get enough information
> for future reference.

You want the message-id on the listing page? Sure, I was doing that
before but I didn't know anyone wanted it and it looked a little
cluttered. Let me know.

> Also, any chance you could use the permanent urls in the thread listing?

Uh, that would be a little tricky because the next/previous wants to go
by message number increment, I think. I could post-process all the HTML
files to do a search/replace.

I think the bigger problem is the threads move around on the thread
pages, and that seems impossible to fix as items are added and removed.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> You want the message-id on the listing page? Sure, I was doing that
> before but I didn't know anyone wanted it and it looked a little
> cluttered. Let me know.

I agree it was too cluttered for normal use.

What I'm trying to do is get a page which has the message-id's of all the
messages and the comments on the same page. That way I can dump the data into
a text file to experiment with.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Gregory Stark wrote:
>> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>>> The comments are stored at JS-Kit:
>>> http://js-kit.com/comments/
>>
>> It's stored in their server?

> Yes, that was the beauty of it --- I just add javascript with a tag and
> all comments are handled by them.

"Beauty"? I don't think we want to rely on non-project-controlled
servers for anything that's part of our core infrastructure. If/when
js-kit.com goes belly-up, what happens to that data? Also, what kind of
privacy guarantees have we got? (Admittedly, privacy may be moot for
information that was originally entered on a public web page, but the
whole idea of someone else controlling our data just makes me itch.)

I can go along with this as a jury-rig setup for our first commit fest,
but it just seems like another powerful argument for moving to something
wiki-based as soon as we can get that sorted.

regards, tom lane

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Gregory Stark wrote:
> >> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
> >>> The comments are stored at JS-Kit:
> >>> http://js-kit.com/comments/
> >>
> >> It's stored in their server?
>
> > Yes, that was the beauty of it --- I just add javascript with a tag and
> > all comments are handled by them.
>
> "Beauty"? I don't think we want to rely on non-project-controlled
> servers for anything that's part of our core infrastructure. If/when
> js-kit.com goes belly-up, what happens to that data? Also, what kind of
> privacy guarantees have we got? (Admittedly, privacy may be moot for
> information that was originally entered on a public web page, but the
> whole idea of someone else controlling our data just makes me itch.)
>
> I can go along with this as a jury-rig setup for our first commit fest,
> but it just seems like another powerful argument for moving to something
> wiki-based as soon as we can get that sorted.

We don't need these comments for more than a few weeks --- I don't see a
problem with it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Gregory Stark wrote:
> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>
> > You want the message-id on the listing page? Sure, I was doing that
> > before but I didn't know anyone wanted it and it looked a little
> > cluttered. Let me know.
>
> I agree it was too cluttered for normal use.
>
> What I'm trying to do is get a page which has the message-id's of all the
> messages and the comments on the same page. That way I can dump the data into
> a text file to experiment with.

Why not grab the mbox file and grep out the message ids?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Gregory Stark wrote:
> >> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
> >>> The comments are stored at JS-Kit:
> >>> http://js-kit.com/comments/
> >>
> >> It's stored in their server?
>
> > Yes, that was the beauty of it --- I just add javascript with a tag and
> > all comments are handled by them.
>
> "Beauty"? I don't think we want to rely on non-project-controlled
> servers for anything that's part of our core infrastructure. If/when
> js-kit.com goes belly-up, what happens to that data? Also, what kind of
> privacy guarantees have we got? (Admittedly, privacy may be moot for
> information that was originally entered on a public web page, but the
> whole idea of someone else controlling our data just makes me itch.)
>
> I can go along with this as a jury-rig setup for our first commit fest,
> but it just seems like another powerful argument for moving to something
> wiki-based as soon as we can get that sorted.

We could move to a wiki if someone finds out how to dump emails into a
wiki, or if we decide to be more structured in our methods, like having
separate URLs for bugs, feature requests, and patches, and doing all
activity on those items at those URLs.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Gregory Stark wrote:
> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>
> > You want the message-id on the listing page? Sure, I was doing that
> > before but I didn't know anyone wanted it and it looked a little
> > cluttered. Let me know.
>
> I agree it was too cluttered for normal use.
>
> What I'm trying to do is get a page which has the message-id's of all the
> messages and the comments on the same page. That way I can dump the data into
> a text file to experiment with.

Oh, what I would really like is to be able to pull up
archives.postgresql.org emails based on message id so I can link to the
entire thread. Unfortunately, it doesn't work there, nor does Google or
any of the other Postgres email archive sites.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> I can go along with this as a jury-rig setup for our first commit fest,
>> but it just seems like another powerful argument for moving to something
>> wiki-based as soon as we can get that sorted.

> We could move to a wiki if someone finds out how to dump emails into a
> wiki, or if we decide to be more structured in our methods, like having
> separate URLs for bugs, feature requests, and patches, and doing all
> activity on those items at those URLs.

I don't think we want to "dump emails into a wiki". What we want is a
page with links into the mail archives plus commentary.

regards, tom lane

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> I can go along with this as a jury-rig setup for our first commit fest,
> >> but it just seems like another powerful argument for moving to something
> >> wiki-based as soon as we can get that sorted.
>
> > We could move to a wiki if someone finds out how to dump emails into a
> > wiki, or if we decide to be more structured in our methods, like having
> > separate URLs for bugs, feature requests, and patches, and doing all
> > activity on those items at those URLs.
>
> I don't think we want to "dump emails into a wiki". What we want is a
> page with links into the mail archives plus commentary.

So the thread titles get put into a wiki that supports comments with
URL links to our archives?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Sun, 16 Mar 2008, Bruce Momjian wrote:

> Oh, what I would really like is to be able to pull up
> archives.postgresql.org emails based on message id so I can link to the
> entire thread. Unfortunately, it doesn't work there, nor does Google or
> any of the other Postgres email archive sites.

This is something I've been looking into my own organization. The message
ids are at the start of the archive web pages. For example your e-mail
here I'm replying to begins like this if you look at the page source:

http://archives.postgresql.org/pgsql-hackers/2008-03/msg00554.php
<!-- MHonArc v2.6.16 -->
<!--X-Subject: Re: Commit fest? -->
<!--X-From-R13: Pehpr [bzwvna <oehprNzbzwvna.hf> -->
<!--X-Date: Sun, 16 Mar 2008 23:19:33 &#45;0300 (ADT) -->
<!--X-Message-Id: 200803170219(dot)m2H2JRQ11863(at)momjian(dot)us -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 20681(dot)1205719990(at)sss(dot)pgh(dot)pa(dot)us -->
<!--X-Head-End-->

I was thinking of writing something that scraped the archives building a
lookup table out of this information. What would be nice is if the
X-Message-Id and X-Reference were both put into the regular HTML for
future archived messages so that it's more likely tools like Google could
search based on them. A brief glance at the MHonArc documentation
suggests that could be run to re-covert any existing messages that are
still available in order to add to those even.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

Greg Smith wrote:
> On Sun, 16 Mar 2008, Bruce Momjian wrote:
>
>> Oh, what I would really like is to be able to pull up
>> archives.postgresql.org emails based on message id so I can link to
>> the entire thread. Unfortunately, it doesn't work there, nor does
>> Google or any of the other Postgres email archive sites.
>
> This is something I've been looking into my own organization. The
> message ids are at the start of the archive web pages. For example your
> e-mail here I'm replying to begins like this if you look at the page
> source:
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00554.php
> <!-- MHonArc v2.6.16 -->
> <!--X-Subject: Re: Commit fest? -->
> <!--X-From-R13: Pehpr [bzwvna <oehprNzbzwvna.hf> -->
> <!--X-Date: Sun, 16 Mar 2008 23:19:33 &#45;0300 (ADT) -->
> <!--X-Message-Id: 200803170219(dot)m2H2JRQ11863(at)momjian(dot)us -->
> <!--X-Content-Type: text/plain -->
> <!--X-Reference: 20681(dot)1205719990(at)sss(dot)pgh(dot)pa(dot)us -->
> <!--X-Head-End-->
>
> I was thinking of writing something that scraped the archives building a
> lookup table out of this information. What would be nice is if the
> X-Message-Id and X-Reference were both put into the regular HTML for
> future archived messages so that it's more likely tools like Google
> could search based on them. A brief glance at the MHonArc documentation
> suggests that could be run to re-covert any existing messages that are
> still available in order to add to those even.

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?

//Magnus

Greg Smith wrote:
> On Sun, 16 Mar 2008, Bruce Momjian wrote:
>
> > Oh, what I would really like is to be able to pull up
> > archives.postgresql.org emails based on message id so I can link to the
> > entire thread. Unfortunately, it doesn't work there, nor does Google or
> > any of the other Postgres email archive sites.
>
> This is something I've been looking into my own organization. The message
> ids are at the start of the archive web pages. For example your e-mail
> here I'm replying to begins like this if you look at the page source:
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00554.php
> <!-- MHonArc v2.6.16 -->
> <!--X-Subject: Re: Commit fest? -->
> <!--X-From-R13: Pehpr [bzwvna <oehprNzbzwvna.hf> -->
> <!--X-Date: Sun, 16 Mar 2008 23:19:33 &#45;0300 (ADT) -->
> <!--X-Message-Id: 200803170219(dot)m2H2JRQ11863(at)momjian(dot)us -->
> <!--X-Content-Type: text/plain -->
> <!--X-Reference: 20681(dot)1205719990(at)sss(dot)pgh(dot)pa(dot)us -->
> <!--X-Head-End-->
>
> I was thinking of writing something that scraped the archives building a
> lookup table out of this information. What would be nice is if the
> X-Message-Id and X-Reference were both put into the regular HTML for
> future archived messages so that it's more likely tools like Google could
> search based on them. A brief glance at the MHonArc documentation
> suggests that could be run to re-covert any existing messages that are
> still available in order to add to those even.

Yep, also you can pull my comments by using the message id, e.g.:

http://js-kit.com/rss/momjian.us/msgid-1195396974(dot)4217(dot)13(dot)camel(at)ebony(dot)site

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Magnus Hagander wrote:
> > I was thinking of writing something that scraped the archives building a
> > lookup table out of this information. What would be nice is if the
> > X-Message-Id and X-Reference were both put into the regular HTML for
> > future archived messages so that it's more likely tools like Google
> > could search based on them. A brief glance at the MHonArc documentation
> > suggests that could be run to re-covert any existing messages that are
> > still available in order to add to those even.
>
> 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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

"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!

Gregory Stark wrote:
> "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?

No, it requires hacking the indexing script, and we'll store the
messageid in it's own column in the table.

//Magnus

On Mon, 17 Mar 2008, 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?

No, using the database for this sort of thing is so old-school at this
point. Didn't you hear that good web applications abstract away the
database so you don't have to worry about what's in there? The right way
to handle this is to push the entire archive through the client each time
so it can make rich decisions about the data instead. I hear Ruby on
Rails is a good tool for this.

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

That would be perfect. I'd like to be able to replace my saved mailbox
with a web page containing links to the archives instead, and that would
be easy to do with that support. Bruce's requirements have a similar
mapping job to accomplish, and I could imagine a useful app for that area
that consumed an mbox file and output a page of wiki markup. Why, the
patch queue is practically on a wiki already!

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

Magnus Hagander wrote:
> Gregory Stark wrote:
> > "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?
>
> No, it requires hacking the indexing script, and we'll store the
> messageid in it's own column in the table.

Yea, it would be nice if we could do it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +