As difficult as it was to reproduce the bug, I'd like a clear cut regression test. The use case where it manifested is fairly rare in normal use - server start after prolonged outage, where the queue of inbound device events is built up enough to make serialization errors more likely. On Jan 14, 2010, at 10:19 AM, Tom Lane wrote:
> BTW --- from my own perspective, what is much more interesting is > testing time on your real application to make sure that you don't > see a crash any more. I am certain that I identified and fixed > *a* bug, what I'm less certain about is that it is actually what > you were hitting. The previous advice would help you reproduce > the bug that I fixed, but ... > > regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
