Re: Recovery from multi trouble
От | Simon Riggs |
---|---|
Тема | Re: Recovery from multi trouble |
Дата | |
Msg-id | 1135248819.2964.422.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Recovery from multi trouble (OKADA Satoshi <okada.satoshi@lab.ntt.co.jp>) |
Ответы |
Re: Recovery from multi trouble
|
Список | pgsql-hackers |
On Mon, 2005-12-19 at 17:17 +0900, OKADA Satoshi wrote: > Tom Lane wrote: > > >OKADA Satoshi <okada.satoshi@lab.ntt.co.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. IMHO the problem is the deletion of the xlog file, not the error message. If you *did* lose an xlog file, would you not expect the system to come up anyway? You're saying that you'd want the system to stay down because of this? Would you want the system to be less available in that circumstance? I guess you want might a new postmaster option: "don't come up if you are damaged". Would you really use that? Overall, thank you for doing the durability testing. It is good to know that you're doing that and taking the time to report any issues you see. Best Regards, Simon Riggs
В списке pgsql-hackers по дате отправления: