From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: random crashes on -HEAD for a few days now |
Date: | 2007-08-20 14:04:26 |
Message-ID: | 29329.1187618666@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> at least one of my buildfarm members (emu) is crashing on what seems
> totally unrelated regression tests for a few days now:
I was wondering about that ...
> it took me about 10 tries to reproduce that manually and I'm getting the
> following stacktrace:
> #0 varbit_out (fcinfo=0x88c75000) at varbit.c:549
> 549 x = *sp;
Just eyeballing that code, it looks like it will try to fetch the byte
immediately beyond the end of the bit array, when the number of bits is
an exact multiple of 8. This is unlikely to cause a problem but it
*could* happen that the input is right up against the end of memory.
Could you check whether that is what happened here? (The important
question is whether the input seems to be sane, ie, "len" isn't huge.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-20 14:09:38 | Re: Why NESTED LOOP Not Allowed for FULL and RIGHT Join. |
Previous Message | Rushabh Lathia | 2007-08-20 14:01:50 | Why NESTED LOOP Not Allowed for FULL and RIGHT Join. |