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

Re: unable to fail over to warm standby server

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Mason Hale <mason(at)onespot(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: unable to fail over to warm standby server
Date: 2010-02-05 11:11:19
Message-ID: 4B6BFCD7.1000709@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Mason Hale wrote:
> Given that this situation did NOT actually cause corruption, rather the
> error message was mangled such that it suggested corruption, I offer this
> revised suggestion for update to the documentation:
> 
> Important note: It is critical the trigger file be created with permissions
>> allowing the postgres process to remove the file. Generally this is best
>> done by creating the file from the postgres user account. Failure to do so
>> will prevent completion of WAL file recovery and the server from coming back
>> online successfully.

Ok, I've added this note to the 8.3 docs now.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

pgsql-bugs by date

Next:From: sulfinuDate: 2010-02-05 11:45:30
Subject: BUG #5315: Unlisted keyword WINDOW
Previous:From: Joe ConwayDate: 2010-02-05 03:13:34
Subject: Re: BUG #5304: psql using conninfo fails in connecting to the server

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