From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Enabling Checksums |
Date: | 2012-12-18 15:47:01 |
Message-ID: | CAM-w4HOn6CWfGwF4+Bg_GLP1B00=c8rZNKY2FyOOuTVRk-j_qQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> There is no good way to make the poor soul who has no standby server
>> happy here. You're just choosing between bad alternatives. The first
>> block error is often just that--the first one, to be joined by others
>> soon afterward. My experience at how drives fail says the second error
>> is a lot more likely after you've seen one.
For what it's worth Oracle allows you to recover a specific block from
backups including replaying the archive logs for that one block.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-18 15:47:13 | Re: configure.in and setproctitle/optreset problem |
Previous Message | Kevin Grittner | 2012-12-18 15:43:01 | Re: Enabling Checksums |