Re: BUG #5269: postgres backend terminates with SIGSEGV - Mailing list pgsql-bugs

From Justin Pitts
Subject Re: BUG #5269: postgres backend terminates with SIGSEGV
Date
Msg-id EA2B064A-2D8C-4948-8F72-C57EFF39863E@bplglobal.net
Whole thread Raw
In response to Re: BUG #5269: postgres backend terminates with SIGSEGV  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
As difficult as it was to reproduce the bug, I'd like a clear cut regressio=
n test. The use case where it manifested is fairly rare in normal use - ser=
ver start after prolonged outage, where the queue of inbound device events =
is built up enough to make serialization errors more likely.=20
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 ...
>=20
>             regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5276: pg_ctl reads data directory on -D instead of postgresql.conf directoryh
Next
From: Justin Pitts
Date:
Subject: Re: BUG #5269: postgres backend terminates with SIGSEGV