Re: Protecting against unexpected zero-pages: proposal - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Protecting against unexpected zero-pages: proposal
Date
Msg-id AANLkTimwMxWe1F94A6ifu0JPJt0zxy=3+CwPwCd3xOZm@mail.gmail.com
Whole thread Raw
In response to Re: Protecting against unexpected zero-pages: proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Nov 10, 2010 at 1:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Once you know that there is, or isn't,
a filesystem-level error involved, what are you going to do next?
You're going to go try to debug the component you know is at fault,
that's what.  And that problem is still AI-complete.


If we know for sure that Postgres was not at fault then we have standby node to failover to, where Postgres warm standby is being maintained by streaming replication.

Regards
--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.EnterpriseDB.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Protecting against unexpected zero-pages: proposal
Next
From: Robert Haas
Date:
Subject: Re: Protecting against unexpected zero-pages: proposal