Re: warm-standby errors

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: sramirez <sramirez(at)vonage(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: warm-standby errors
Date: 2009-05-11 19:58:33
Message-ID: 1242071913.3843.171.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Mon, 2009-05-11 at 13:50 -0400, sramirez wrote:

> Short of copying the data files elsewhere and doing a row-level
> comparison of the data, is there any way I can check to see if there is
> actual corruption in the warm standby server?

Right now, Warm Standby has same functionality as equivalent Oracle
feature - i.e. no way to confirm absence of corruption. However, WAL
records contain CRC checks that ensure the transferred data is correct,
which is more than most other replication techniques posess. Hot Standby
will allow access to data blocks to allow them to be read and checked,
though that is also possible with an external utility to some extent.

It probably isn't practical with any replication system to confirm the
exact contents of both nodes while replication is running at reasonable
speed. Some heuristics may be possible.

Do you have anything in mind, other than "detect corruption"?

> How can I prevent this
> error from occurring ?

You haven't shown us the error, just what happens afterwards.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message sramirez 2009-05-11 20:32:05 Re: warm-standby errors
Previous Message BRUSSER Michael 2009-05-11 18:10:26 Build and install - how to avoid dependency on specific library version