Re: Two problems when using Postgresql8.3.7, Please help me!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Richard" <husttripper(at)vip(dot)sina(dot)com>
Cc: "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Two problems when using Postgresql8.3.7, Please help me!
Date: 2010-08-03 16:53:21
Message-ID: 22233.1280854401@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Richard" <husttripper(at)vip(dot)sina(dot)com> writes:
> 1.To add live HA to PG, I transfer WAL of a database instance(Primary node) to another database instance (standby node) at real time, and keep startup alive in standby node to recovery WAL online,so that standby node can be a hot standby.
> But I got some trouble. When standby node switch to primary mode to accept connections, of course after startup initilize the WAL and exit, the postgres process ereportERROR
> when mdread function enter ERROR branch, and I got message like this "could not read block X of relation X/X/X: read only Xof X bytes". I spent two days to figure out what happened, but it is too hard.Please help me.

I wonder whether your problem is related to this 8.3.8 bug fix:

* Force WAL segment switch during pg_start_backup() (Heikki)

This avoids corner cases that could render a base backup unusable.

I'd suggest updating to 8.3.latest and making sure that you are taking
the base backup according to the documented procedure. The symptoms you
are mentioning could definitely be caused by starting from an
inconsistent backup.

regards, tom lane

PS: Please do not post the same question to multiple mailing lists.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message ChronicDB Community Team 2010-08-03 17:29:00 Re: Dynamic data model, locks and performance
Previous Message ChronicDB Community Team 2010-08-03 16:52:18 Re: alter table set tablespace