Re: BUG #1678: pw_shadow BUS ERROR - Mailing list pgsql-bugs

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=20

> -----Original Message-----
> From: pgsql-bugs-owner@postgresql.org=20
> [mailto:pgsql-bugs-owner@postgresql.org] 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
>=20
>=20
> The following bug has been logged online:
>=20
> Bug reference:      1678
> Logged by:          Haluk GUNCER
> Email address:      halukguncer@hotmail.com
> PostgreSQL version: 7.4 to 8.0.3
> Operating system:   HP-UX B.11.11
> Description:        pw_shadow BUS ERROR
> Details:=20
>=20
> the system is a high end system used in a major project in=20
> TURKEY. HP guys could not figure it out.
>=20
>=20=20
> Version 7.3.10 works fine.
> version 7.4.8 ,8.0.0 and 8.0.3 never starts.
>=20
> $ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
>=20
> The files belonging to this database system will be owned by=20
> user "postgres".
> This user must also own the server process.
>=20
> The database cluster will be initialized with locale C.
>=20
> fixing permissions on existing directory=20
> /usr/local/pgsql/data ... ok creating directory=20
> /usr/local/pgsql/data/global ... ok creating directory=20
> /usr/local/pgsql/data/pg_xlog ... ok creating directory=20
> /usr/local/pgsql/data/pg_xlog/archive_status ... ok creating=20
> directory /usr/local/pgsql/data/pg_clog ... ok creating=20
> directory /usr/local/pgsql/data/pg_subtrans ... ok creating=20
> directory /usr/local/pgsql/data/base ... ok creating=20
> directory /usr/local/pgsql/data/base/1 ... ok creating=20
> directory /usr/local/pgsql/data/pg_tblspc ... ok selecting=20
> default max_connections ... 100 selecting default=20
> shared_buffers ... 1000 creating configuration files ... ok=20
> creating template1 database in /usr/local/pgsql/data/base/1=20
> ... ok initializing pg_shadow ... sh: 2419 Bus=20
> error(coredump) child process exited with exit code 138
> initdb: removing contents of data directory "/usr/local/pgsql/data"
>=20
> *************************************
>=20
> After BUS ERROR semafore remains.
> have to be removed with "ipcrm".
>=20
> /home/postgres$ipcs -a | grep post
> m      61447 0x00000001 --rw-------  postgres       dba=20=20
> postgres       dba
>  0   10403840  2419  2419 18:14:36 no-entry 18:14:36
> s     331802 0x00000002 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     442395 0x00000003 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     401436 0x00000004 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     372765 0x00000005 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     352286 0x00000006 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     352287 0x00000007 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
> s     352288 0x00000008 --ra-------  postgres       dba=20=20
> postgres       dba=20
>   1
> 7 18:14:36 18:14:36
>=20
> ---------------------------(end of=20
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index=20
> scan if your
>       joining column's datatypes do not match
>=20
>=20