The following bug has been logged online:
Bug reference: 5269
Logged by: Justin Pitts
Email address: justinpi...@gmail.com
PostgreSQL version: 8.4.2
Operating system: Debian Lenny 2.6.30-bpo.1-amd-64 kernel
Description:postgres backend terminates with SIGSEGV
Details
Sorry for the delay.
I am attempting to construct a JDBC test case that reproduces the problem.
I have installed the patch and have not seen the crash since.
On Jan 13, 2010, at 11:58 AM, Tom Lane wrote:
> I wrote:
>> After puzzling over this for many hours, I have a theory that seems to
>> fi
ublic static void main(String... args) throws SQLException,
InterruptedException {
Bug5269Test test = new Bug5269Test();
test.test();
}
}
On Jan 13, 2010, at 10:22 PM, Justin Pitts wrote:
> Sorry for the delay.
>
> I am attempt
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
On Jan 14, 2010, at 10:16 AM, Tom Lane wrote:
> Justin Pitts writes:
>> My guess is that I am not provoking a 'SI queue overrun'
>
> The 100 temp table creations probably will do that just fine.
>
Is there a way to verify this?
>> Am I completely
On Jan 14, 2010, at 10:44 AM, Tom Lane wrote:
> Justin Pitts writes:
>> On Jan 14, 2010, at 10:16 AM, Tom Lane wrote:
>>> The 100 temp table creations probably will do that just fine.
>
>> Is there a way to verify this?
>
> You could add an elog(LOG, &quo
