Re: Getting a bug tracker for the Postgres project
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Joe Abbate <jma@freedomcircle.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Kim Bisgaard <kim+pg@alleroedderne.adsl.dk>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>, Greg Stark <gsstark@mit.edu>, pgsql-hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2011-05-31T18:13:43Z
Lists: pgsql-hackers
On Tue, May 31, 2011 at 19:59, Joe Abbate <jma@freedomcircle.com> wrote: > On 05/31/2011 01:13 PM, Magnus Hagander wrote: >> Just to be clear, crawling the current archives for this info is >> probably the easiest part of the whole project. In fact, the majority >> of the information you'd need is *already* in a postgresql database on >> search.postgresql.org. > > Does that database have the bug number, PG version and OS as separate > columns, or is it simply an index over all the messages across all the > lists? I think a table just of bug info would be useful at this time, > e.g., to load a potential candidate. However, the message database --if > it includes the message bodies-- would obviously be easier to work with > than web crawling. It does not have all those details, but it has the sender, subject and bodies broken out. So it's definitely an easier starting point. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/