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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
