Hi,
We suspect the problem is not in that area, because we used pg_basebackup o=
n the same database pair under 9.1 and did not have any such problems.=20
Looking at the context of the crashes, they seem to relate to handling of v=
isibility maps during WAL replay. Going by the 9.2 release notes that is an=
area that was changed to allow index-only scans in 9.2.
Also, we can see that 9.2.3 has been released now and has a number of fixes=
relating to WAL replay, so we have decided to try again using that. We wil=
l scrub the standby and make a fresh copy using pg_basebackup. If that does=
n't work then we may try using rsync instead.
We'll let you all know the result.
Regards // Mike
-----Original Message-----
From: Magnus Hagander [mailto:magnus@hagander.net]=20
Sent: Thursday, 7 February 2013 11:49 PM
To: amutu
Cc: Michael Harris; pgsql-general@postgresql.org; Hari Babu
Subject: Re: [GENERAL] Hot Standby has PANIC: WAL contains references to in=
valid pages
On Thu, Feb 7, 2013 at 7:39 AM, amutu <zhao6014@gmail.com> wrote:
> maybe pg_basebackup can`t handle such big database.try=20
> rsync,pg_start_backup,rsync,pg_stop_backup,it always works fine for=20
> us.our instance is about 2TB and we use pg9.1.x.
It really should handle that without problem, but sure, it might be worth t=
rying that one. If you can show that the problem is in pg_basebackup, that'=
s a very clear bug (either in pg_basebackup or in the backend supporting co=
de), so that would be good to know.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
