From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tomas Szepe <szepe(at)pinerecords(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: segfault at aset.c:539 |
Date: | 2003-07-14 17:30:28 |
Message-ID: | 9971.1058203828@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tomas Szepe <szepe(at)pinerecords(dot)com> writes:
> (BTW, it seems the bug can't be triggered on Linux/sparc32).
You'd be less likely to see it on a machine where MAXALIGN is 8,
since there would be more pad bytes on the average ... but depending
on the string length fed to to_ascii(), I think it could be made
to happen on any platform. Strings whose length is an odd multiple
of four (4, 12, etc) would have no pad bytes on any platform.
I'm surprised we did not notice this case when we were testing the fix
for the other bug. That bug was only an off-by-one, this was an
off-by-four :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-14 18:34:57 | Re: [GENERAL] Backwards index scan |
Previous Message | Tomas Szepe | 2003-07-14 17:19:49 | Re: segfault at aset.c:539 |