Bruce Momjian writes:

> Can someone point me to a bug that is _not_ on the TODO list?

Just looking through pgsql-bugs of the last two weeks, the following all
look reasonable.

http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00088.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00084.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00078.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00089.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00086.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00042.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00036.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00035.html
http://www.ca.postgresql.org/mhonarc/pgsql-bugs/2001-08/msg00012.html

At least a couple of them I would want to have recorded somewhere.

> If not, what does a complete bug database do for us except list
> reported bugs and possible workarounds.

history, searchability

-- 
Peter Eisentraut   [EMAIL PROTECTED]   http://funkturm.homeip.net/~peter


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to