| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | InitBufferPoolAccess crash |
| Date: | 2006-05-09 17:18:22 |
| Message-ID: | 200605091118.22709.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I have a 7.3.4 cluster that just sigsegv'd. I know an
upgrade is desperately needed. In the meantime, does the
following gdb output provide any clues as to what we might
be able to do to nurse it along until we upgrade?
Thanks,
Ed
PostgreSQL 7.3.4 on hppa2.0w-hp-hpux11.00, compiled by GCC gcc (GCC) 3.2.2
(gdb) core-file core
Core was generated by `postgres'.
Program terminated with signal 11, Segmentation fault.
warning: The shared libraries were not privately mapped; setting a
breakpoint in a shared library will not work until you rerun the program.
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...#0 0x12d288 in InitBufferPoolAccess ()
from /opt/pgsql/installs/postgresql-7.3.4/bin/postmaster
(gdb) bt
#0 0x12d288 in InitBufferPoolAccess ()
from /opt/pgsql/installs/postgresql-7.3.4/bin/postmaster
Error accessing memory address 0x0: Invalid argument.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2006-05-09 17:52:45 | Re: Arguments Pro/Contra Software Raid |
| Previous Message | Joshua D. Drake | 2006-05-09 17:00:31 | Re: pg_dump and grants to PUBLIC |