Re: bugs that have not been replied-to on list

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: bugs that have not been replied-to on list
Date: 2010-04-29 00:33:22
Message-ID: v2q603c8f071004281733v2c419e2fhbc1696434188b1a5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Apr 28, 2010 at 4:09 PM, Dimitri Fontaine
<dfontaine(at)hi-media(dot)com> wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe
>> the other lists in the future as well) so the workflow would look like
>> this:
>
> Well there is a WIP to use an ArchiveOpteryX based solution to replace
> the archives and get rid of the artificial breaking of pages. My guess
> is that adding a status table linking to emails and that a set of
> volunteers (they gave their names!) maintain would make our day.

It would be great to leverage that. Is there any chance of that
getting finalized and deployed to production some time in the
forseeable future?

...Robert

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message sibal 2010-04-29 08:33:58 BUG #5441: Why Not?????
Previous Message Tom Lane 2010-04-28 21:20:17 Re: BUG #5417: intarray adds <@ operator which breaks infromation_schema.referential_constraints