Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Recovery from multi trouble
- From: OKADA Satoshi <okada(dot)satoshi(at)lab(dot)ntt(dot)co(dot)jp>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Recovery from multi trouble
- Date: Mon, 19 Dec 2005 17:17:40 +0900
- Message-id: <43A66CA4(dot)2010603(at)lab(dot)ntt(dot)co(dot)jp>
Tom Lane wrote: >OKADA Satoshi <okada(dot)satoshi(at)lab(dot)ntt(dot)co(dot)jp> writes: > > >>The loss of log was simulated by deleting the latest xlog file. >> >> > >What does that have to do with reality? Postgres is very careful not to >use an xlog file until it's been fully metadata-synced. You might as >well complain that PG doesn't recover after "rm -rf /" ... > > In this case(postmaster abnormal end ,and log is lost), I understand that database cannot recover normally. Though a database cannot recover normally, postmaster does not output a clear message showing this situation. I think that it is a problem. Thanks, OKADA Satoshi
- Follow-Ups:
- Re: Recovery from multi trouble
- From: Simon Riggs
- Re: Recovery from multi trouble
- References:
- Recovery from multi trouble
- From: OKADA Satoshi
- Re: Recovery from multi trouble
- From: Tom Lane
- Recovery from multi trouble
- Prev by Date: Re: [pgadmin-hackers] Client-side password encryption
- Next by Date: Re: [pgadmin-hackers] Client-side password encryption
- Previous by thread: Re: Recovery from multi trouble
- Next by thread: Re: Recovery from multi trouble
- Indexes: