I agree with you totally.
Don't yet know how to implement it, and don't have much spare time to do so
yet either. I'm working on some stuff which will mean there are more people
to help with the techdocs site and get things done (if it works), therefore
improving the present techdocs system of showing known bugs and fixes, etc.
But it's going to take a few months of effort.
Regards and best wishes,
On Friday 22 February 2002 23:17, Andy Marden wrote:
> 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 techdocs.postgresql.org 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
In response to
pgsql-bugs by date
|Next:||From: Justin||Date: 2002-02-26 04:05:32|
|Subject: Re: Trying Cygwin version of PostgreSQL again|
|Previous:||From: Tom Lane||Date: 2002-02-25 23:29:11|
|Subject: Re: Possible bug concerning LASTOID in 7.2 |