Skip site navigation (1) Skip section navigation (2)

Re: Getting a bug tracker for the Postgres project

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Joe Abbate <jma(at)freedomcircle(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Kim Bisgaard <kim+pg(at)alleroedderne(dot)adsl(dot)dk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Getting a bug tracker for the Postgres project
Date: 2011-05-31 18:13:43
Message-ID: BANLkTiniiWnqDfNc8DPaw=JT4sB3E6m3YQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, May 31, 2011 at 19:59, Joe Abbate <jma(at)freedomcircle(dot)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/

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2011-05-31 18:14:26
Subject: Re: Getting a bug tracker for the Postgres project
Previous:From: Alvaro HerreraDate: 2011-05-31 18:05:45
Subject: Re: Getting a bug tracker for the Postgres project

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group