| 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: | 2005-12-19 08:17:40 |
| Message-ID: | 43A66CA4.2010603@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-12-19 08:51:23 | Re: [pgadmin-hackers] Client-side password encryption |
| Previous Message | Tom Lane | 2005-12-19 05:37:22 | Re: [pgadmin-hackers] Client-side password encryption |