| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | OKADA Satoshi <okada(dot)satoshi(at)lab(dot)ntt(dot)co(dot)jp>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Recovery from multi trouble |
| Date: | 2006-03-27 15:26:47 |
| Message-ID: | 14505.1143473207@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Mon, 2006-03-27 at 12:14 +0900, OKADA Satoshi wrote:
>> Our aim is giving database recovery chances to a database administrator
>> at PostgreSQL startup time when there is possibility of data loss of
>> losing log files.
> There is no possibility of data loss because of loss of a single log
> file, if you have your hardware configured correctly.
I'm fairly concerned about whether this isn't just replacing one failure
mode with another one. See nearby discussion with Alex Bahdushka for a
graphic reminder why PANICing on any little thing during WAL replay is
not necessarily such a great idea.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-27 15:31:47 | Re: Shared memory |
| Previous Message | Tom Lane | 2006-03-27 15:22:49 | Re: [GENERAL] PANIC: heap_update_redo: no block |