Postgres Pro
Downloads
Home   >   mailing lists

BUG #6671: Killed restore command causes postmaster to exit - Mailing list pgsql-bugs

From edward@heroku.com
Subject BUG #6671: Killed restore command causes postmaster to exit
Date
Msg-id E1SaAXd-00072t-4n@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #6671: Killed restore command causes postmaster to exit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
The following bug has been logged on the website:

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

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

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

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Next
From: Postgres User
Date:
Subject: Re: BUG #6668: hashjoin cost problem