I've seen this before, and that was due to unaligned memory access, which is not supported on some platforms.
I thought we didn't do unaligned memory access?? ... John > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Haluk GUNCER > Sent: Wednesday, May 25, 2005 1:23 AM > To: pgsql-bugs@postgresql.org > Subject: [BUGS] BUG #1678: pw_shadow BUS ERROR > > > The following bug has been logged online: > > Bug reference: 1678 > Logged by: Haluk GUNCER > Email address: [EMAIL PROTECTED] > PostgreSQL version: 7.4 to 8.0.3 > Operating system: HP-UX B.11.11 > Description: pw_shadow BUS ERROR > Details: > > the system is a high end system used in a major project in > TURKEY. HP guys could not figure it out. > > > Version 7.3.10 works fine. > version 7.4.8 ,8.0.0 and 8.0.3 never starts. > > $ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data > > The files belonging to this database system will be owned by > user "postgres". > This user must also own the server process. > > The database cluster will be initialized with locale C. > > fixing permissions on existing directory > /usr/local/pgsql/data ... ok creating directory > /usr/local/pgsql/data/global ... ok creating directory > /usr/local/pgsql/data/pg_xlog ... ok creating directory > /usr/local/pgsql/data/pg_xlog/archive_status ... ok creating > directory /usr/local/pgsql/data/pg_clog ... ok creating > directory /usr/local/pgsql/data/pg_subtrans ... ok creating > directory /usr/local/pgsql/data/base ... ok creating > directory /usr/local/pgsql/data/base/1 ... ok creating > directory /usr/local/pgsql/data/pg_tblspc ... ok selecting > default max_connections ... 100 selecting default > shared_buffers ... 1000 creating configuration files ... ok > creating template1 database in /usr/local/pgsql/data/base/1 > ... ok initializing pg_shadow ... sh: 2419 Bus > error(coredump) child process exited with exit code 138 > initdb: removing contents of data directory "/usr/local/pgsql/data" > > ************************************* > > After BUS ERROR semafore remains. > have to be removed with "ipcrm". > > /home/postgres$ipcs -a | grep post > m 61447 0x00000001 --rw------- postgres dba > postgres dba > 0 10403840 2419 2419 18:14:36 no-entry 18:14:36 > s 331802 0x00000002 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 442395 0x00000003 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 401436 0x00000004 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 372765 0x00000005 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 352286 0x00000006 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 352287 0x00000007 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > s 352288 0x00000008 --ra------- postgres dba > postgres dba > 1 > 7 18:14:36 18:14:36 > > ---------------------------(end of > broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index > scan if your > joining column's datatypes do not match > > ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
