Re: BUG #5140: initdb crashes - Mailing list pgsql-bugs

On Tue, Oct 27, 2009 at 10:47 AM, Marcus Lundblad
<marcus.lundblad@mogul.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05140
> Logged by: =A0 =A0 =A0 =A0 =A0Marcus Lundblad
> Email address: =A0 =A0 =A0marcus.lundblad@mogul.com
> PostgreSQL version: 8.3.8
> Operating system: =A0 Solaris 10
> Description: =A0 =A0 =A0 =A0initdb crashes
> Details:
>
> Hi
>
> I compiled version 8.3.8 of postgres on a Solaris 10 machine.
> When running initdb it crashes like this:
>
> postgres@webbkartbas02> /usr/local/postgres/bin/initdb -D
> /usr/local/postgres/data/ -d
> Running in debug mode.
> VERSION=3D8.3.8
> PGDATA=3D/usr/local/postgres/data
> share_path=3D/usr/local/postgres/share
> PGPATH=3D/usr/local/postgres/bin
> POSTGRES_SUPERUSERNAME=3Dpostgres
> POSTGRES_BKI=3D/usr/local/postgres/share/postgres.bki
> POSTGRES_DESCR=3D/usr/local/postgres/share/postgres.description
> POSTGRES_SHDESCR=3D/usr/local/postgres/share/postgres.shdescription
> POSTGRESQL_CONF_SAMPLE=3D/usr/local/postgres/share/postgresql.conf.sample
> PG_HBA_SAMPLE=3D/usr/local/postgres/share/pg_hba.conf.sample
> PG_IDENT_SAMPLE=3D/usr/local/postgres/share/pg_ident.conf.sample
> 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.
> The default database encoding has accordingly been set to SQL_ASCII.
> The default text search configuration will be set to "english".
>
> fixing permissions on existing directory /usr/local/postgres/data ... ok
> creating subdirectories ... ok
> selecting default max_connections ... 100
> selecting default shared_buffers/max_fsm_pages ... 32MB/204800
> creating configuration files ... ok
> creating template1 database in /usr/local/postgres/data/base/1 ... DEBUG:
> invoking IpcMemoryCreate(size=3D38264832)
> DEBUG: =A0creating and filling new WAL file
> DEBUG: =A0done creating and filling new WAL file
> LOG: =A0database system was shut down at 2009-10-27 15:26:27 CET
> LOG: =A0incorrect resource manager data checksum in record at 0/20
> LOG: =A0invalid primary checkpoint record
> LOG: =A0invalid secondary checkpoint link in control file
> PANIC: =A0could not locate a valid checkpoint record
> Abort - core dumped
> child process exited with exit code 134
> initdb: removing contents of data directory "/usr/local/postgres/data"
>
> The following params to ./configure was passed when compiling postgres:
>
> ./configure --prefix=3D/usr/local/postgres/ --with-pam
> --with-libedit-preferred --with-libxml --with-libxslt --with-gssapi
> --enable-thread-safety
> --enable-dtrace--with-includes=3D/usr/local/include:/usr/include:/usr/gcc=
/incl
> ude:/usr/sfw/include/ --with-libs=3D/usr/local/lib:/usr/gcc/lib:/usr/lib
> --with-libraries=3D/usr/local/lib:/usr/gcc/lib:/usr/lib
>
> the version of gcc is:
> sparc-sun-solaris2.10-gcc (GCC) 4.2.1 (20090222) (gccfss)

Can you get a backtrace from the core dump?

...Robert