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

Re: Full bug list

From: "Andy Marden" <amarden(at)usa(dot)net>
To: "Justin" <aa2(at)bigpond(dot)net(dot)au>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Full bug list
Date: 2002-02-22 12:17:59
Message-ID: 00a601c1bb9a$f848c1c0$0100000a@marden1 (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
It would be useful to be able to search a list of known bugs for
the version of postgresql that you're running. Upgrading to the
latest version to see if it sorts out a problem isn't always a
sensible option..
----- Original Message -----
From: "Justin" <aa2(at)bigpond(dot)net(dot)au>
To: "Andy Marden" <amarden(at)usa(dot)net>; <pgsql-bugs(at)postgresql(dot)org>
Sent: Friday, February 22, 2002 3:24 AM
Subject: Re: Full bug list

> Hi Andy,
> Thats the reason which started for,
but since it's
> grown to encompass so many things, that section hasn't been
updated in ages.
> :-(
> Perhaps its time to look at a better way of keeping it
> :-)
> Regards and best wishes,
> Justin Clift
> On Thursday 21 February 2002 20:32, Andy Marden wrote:
> > Is there a repository on the web somewhere of all the bugs
found, versions
> > they are found against and what theire status is?
> >
> >
> >
> > ---------------------------(end of
> > TIP 2: you can get off all lists at once with the unregister
> >     (send "unregister YourEmailAddressHere" to


pgsql-bugs by date

Next:From: Nicolas PaymalDate: 2002-02-22 13:38:53
Subject: CURRENT_TIMESTAMP not work correctly insinde a transaction.
Previous:From: Heiko LehmannDate: 2002-02-22 10:45:36
Subject: Patch pgsql-7.2 AuthBlockSig

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