On Tue, May 25, 2010 at 11:26, Alex Hunsaker <badalex@gmail.com> wrote:
> On Tue, May 25, 2010 at 10:39, Vlad Romascanu <vromascanu@accurev.com> wrote:
>
>> The following reproducibly crashes Postgres 8.4.3 (segfault) inside
>> int84eq() on both Windows and Linux, but works just fine in 8.3.4:
>
> Hrm... Both work for me (8.4.3 and 8.4.4).
Ahh it breaks on 32 bit
Program received signal SIGSEGV, Segmentation fault.
0x08276adf in int84eq (fcinfo=0xbfad27cc) at int8.c:271
271 PG_RETURN_BOOL(val1 == val2);
(gdb) bt
#0 0x08276adf in int84eq (fcinfo=0xbfad27cc) at int8.c:271
#1 0x082ee0bb in FunctionCall2 (flinfo=0x8923578, arg1=2, arg2=1) at
fmgr.c:1309
#2 0x0818c27e in execTuplesMatch (slot1=0x89228b8, slot2=0x8922878,
numCols=1, matchColIdx=0x891e628, eqfunctions=0x8923578,
evalContext=0x890c720)
at execGrouping.c:97
#3 0x081a479b in ExecUnique (node=0x8922e08) at nodeUnique.c:88
#4 0x08190278 in ExecProcNode (node=0x8922e08) at execProcnode.c:439
#5 0x081a2a6b in ExecNestLoop (node=0x8922c78) at nodeNestloop.c:120
#6 0x081902f8 in ExecProcNode (node=0x8922c78) at execProcnode.c:404
#7 0x0818f368 in ExecutePlan (queryDesc=0x891ab98,
direction=ForwardScanDirection, count=0) at execMain.c:1504