From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | osprey dumped core on 8.2 |
Date: | 2007-02-23 15:43:08 |
Message-ID: | 20070223154308.GA17656@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Osprey is a NetBSD running on m68k
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=osprey&dt=2007-02-22%2023:00:18
It dumped core running VACUUM:
--- 1,5 ----
VACUUM;
! server closed the connection unexpectedly
! This probably means the server terminated abnormally
! before or while processing the request.
! connection to server was lost
The stack trace report looks incomplete:
================== stack trace: pgsql.27009/src/test/regress/tmp_check/data/postgres.core ==================
Core was generated by `postgres'.
Program terminated with signal 11, Segmentation fault.
#0 0x001f74d6 in AllocSetAlloc (context=0x307d10, size=16777212) at aset.c:546
546 if (set->blocks != NULL)
It's missing the "bt" part.
I don't understand how can this happen, given that "set" cannot be NULL
at this point.
--
Alvaro Herrera http://www.amazon.com/gp/registry/CTMLCN8V17R4
"Puedes elegir el color de tu auto -- siempre y cuando sea negro."
(Henry Ford)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-02-23 15:50:00 | Re: Simple Column reordering |
Previous Message | Alvaro Herrera | 2007-02-23 15:30:40 | Re: SCMS question |