Marshall, Steve wrote: > Any thoughts on whether or not this patch should be included in a future > PostgreSQL release? If so, any thoughts on additional testing, etc, > that needs to be done? Should the patch be added to a minor release of > 8.3, or only included forward in 8.4? In my opinion, this is a pretty > serious error causing some major problems and workarounds in systems I > am working on, should I would vote for inclusion in minor releases. > > The post below seems to have become disassociated from the rest of the > thread on this bug, perhaps because it was issued in February, and the > rest of the thread was posted in January. Is there any way to make the > mailing list archives link these messages back to the rest of the > thread?
I am tracking this item and was waiting for someone to reply to it. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
