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

BUG #6671: Killed restore command causes postmaster to exit

From: edward(at)heroku(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6671: Killed restore command causes postmaster to exit
Date: 2012-05-31 18:56:13
Message-ID: E1SaAXd-00072t-4n@wrigleys.postgresql.org (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-bugs
The following bug has been logged on the website:

Bug reference:      6671
Logged by:          Ed Muller
Email address:      edward(at)heroku(dot)com
PostgreSQL version: 9.0.7
Operating system:   Linux (Ubuntu 10.04)
Description:        

We have this thing where we kill the restore command sometimes, to ensure
it's not stuck. 

This has rarely led to postmaster dying afterwards instead of retrying.

Here are some related logs...

[CRIMSON] LOG:  restored log file "00000006000031B500000099" from archive

[CRIMSON] FATAL:  could not restore file "00000006000031B50000009A" from
archive: return code 36608

[CRIMSON] LOG:  startup process (PID 854) exited with exit code 1

[CRIMSON] LOG:  terminating any other active server processes


Responses

pgsql-bugs by date

Next:From: Adrian KlaverDate: 2012-05-31 20:37:09
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Previous:From: Bruce MomjianDate: 2012-05-31 18:53:42
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2

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