Skip site navigation (1) Skip section navigation (2)

postgres 9.0 crash when bringing up hot standby

From: Alanoly Andrews <alanolya(at)invera(dot)com>
To: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: postgres 9.0 crash when bringing up hot standby
Date: 2010-08-06 13:10:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-hackers

OS level = AIX 5.3 ML-8
Postgres version = 9.0 beta-4

I'm testing "hot standby" using "streaming WAL records". On trying to bring up the hot standby, I see the following error in the log:

LOG:  database system was interrupted; last known up at 2010-08-05 14:46:36 EDT
LOG:  entering standby mode
LOG:  restored log file "000000010000000000000007" from archive
LOG:  redo starts at 0/7000020
LOG:  consistent recovery state reached at 0/8000000
LOG:  database system is ready to accept read only connections
cp: /pgarclog/pg1/000000010000000000000008: A file or directory in the path name does not exist.
LOG:  WAL receiver process (PID 1073206) was terminated by signal 11
LOG:  terminating any other active server processes

There is a core dump. The debugger indicates the crash sequence as follows:

(dbx) where
_alloc_initial_pthread(??) at 0x90000000049567c
__pth_init(??) at 0x900000000493ba4
uload(??, ??, ??, ??, ??, ??, ??, ??) at 0x9fffffff0001954
load_64.load(??, ??, ??) at 0x90000000004686c
loadAndInit() at 0x90000000047bd7c
dlopen(??, ??) at 0x90000000011cc4c
internal_load_library(libname = "/apps/pg_9.0_b4/lib/postgresql/"), line 234 in "dfmgr.c"
load_file(filename = "libpqwalreceiver", restricted = '\0'), line 156 in "dfmgr.c"
WalReceiverMain(), line 248 in "walreceiver.c"
AuxiliaryProcessMain(argc = 2, argv = 0x0fffffffffffa8b8), line 428 in "bootstrap.c"
StartChildProcess(type = WalReceiverProcess), line 4405 in "postmaster.c"
sigusr1_handler(postgres_signal_arg = 30), line 4227 in "postmaster.c"
__fd_select(??, ??, ??, ??, ??) at 0x90000000011805c = 5, __readlist = 0x0fffffffffffd0a8, __writelist = (nil), __exceptlist = (nil), __timeout = 0x0ffffffffffff0c0), line 229 in "time.h"
unnamed block in ServerLoop(), line 1391 in "postmaster.c"
unnamed block in ServerLoop(), line 1391 in "postmaster.c"
ServerLoop(), line 1391 in "postmaster.c"
PostmasterMain(argc = 1, argv = 0x00000001102aa4b0), line 1092 in "postmaster.c"
main(argc = 1, argv = 0x00000001102aa4b0), line 188 in "main.c"

Any pointers on how to resolve the issue will be much appreciated.


Alanoly Andrews (alanolya(at)invera(dot)com<mailto:alanolya(at)invera(dot)com>)
Senior Software Engineer
Invera Inc.
Montreal, QC

This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Ce courriel est confidentiel et protg. L'expditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) dsign(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immdiatement, par retour de courriel ou par un autre moyen.


pgsql-hackers by date

Next:From: Mike FowlerDate: 2010-08-06 13:43:52
Subject: Re: review: xml_is_well_formed
Previous:From: Fujii MasaoDate: 2010-08-06 12:54:55
Subject: default of max_stack_depth

pgsql-admin by date

Next:From: Fujii MasaoDate: 2010-08-06 14:31:03
Subject: Re: postgres 9.0 crash when bringing up hot standby
Previous:From: Silvio BrandaniDate: 2010-08-06 11:56:53
Subject: Re: out of memory error

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group