| From: | Justin Pitts <jpitts(at)bplglobal(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgreSQL(dot)org |
| Subject: | Re: BUG #5269: postgres backend terminates with SIGSEGV |
| Date: | 2010-01-14 15:25:46 |
| Message-ID: | EA2B064A-2D8C-4948-8F72-C57EFF39863E@bplglobal.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pitts | 2010-01-14 15:34:10 | Re: BUG #5269: postgres backend terminates with SIGSEGV |
| Previous Message | Tom Lane | 2010-01-14 15:19:22 | Re: BUG #5269: postgres backend terminates with SIGSEGV |