Re: BUG #7597: exception 0xC0000005

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Bo Thorbjørn Jensen <bo(at)budget123(dot)dk>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #7597: exception 0xC0000005
Date: 2012-10-11 14:18:31
Message-ID: 261.1349965111@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 11.10.2012 14:42, Craig Ringer wrote:
>> No crash here on version() = PostgreSQL 9.1.5 on
>> x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.7.0 20120507 (Red Hat
>> 4.7.0-5), 64-bit

> I can reproduce this on my Windows box with the script Bo provided, with
> a fresh checkout from git master branch. Stack trace looks like this:

I see it too. I think the crash probably only occurs on a 32-bit build
(or one where you've disabled int8-pass-by-value anyway). Looks like
something's confused about cross-data-type comparisons --- this is an
int4 vs int8 comparison, so it shouldn't be ending up at int8eq.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2012-10-11 14:52:40 Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous Message Heikki Linnakangas 2012-10-11 13:00:31 Re: BUG #7597: exception 0xC0000005