Обсуждение: BUG #6736: Hot-standby replica crashed after failover:

Поиск
Список
Период
Сортировка

BUG #6736: Hot-standby replica crashed after failover:

От
maxim.boguk@gmail.com
Дата:
The following bug has been logged on the website:

Bug reference:      6736
Logged by:          Maksym Boguk
Email address:      maxim.boguk@gmail.com
PostgreSQL version: 9.0.4
Operating system:   FreeBSD
Description:=20=20=20=20=20=20=20=20

Hi,

May be it was fixed in more recent releases, but I can not find related
things in release notices.

The next sequence leads to the standby crash after failover:

1)stop master (wait untill full stop)
2)initiate failover
hot-standby crashed during failover,
however successfully started after manual start (and seems work without any
future errors).

In hot-standby logs:
2012-07-13 17:06:08.199 MSK 58208 @ from  [vxid: txid:0] []FATAL:=20
replication terminated by primary server
2012-07-13 17:06:08.788 MSK 67891 @ from  [vxid: txid:0] []FATAL:  could not
connect to the primary server: server closed the connection unexpectedly
2012-07-13 17:06:19.521 MSK 67912 @ from  [vxid: txid:0] []FATAL:=20
terminating walreceiver process due to administrator command
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
2026 of relation base/14482918/32905335 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
7327 of relation base/14482918/32905343 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
7299 of relation base/14482918/32905343 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
2040 of relation base/14482918/32905335 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
1761 of relation base/16424/33266809 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []WARNING:  page
1750 of relation base/16424/33266809 was uninitialized
2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []PANIC:  WAL
contains references to invalid pages
2012-07-13 17:06:19.895 MSK 67435 pgsql@pgsql from [local] [vxid:2/0 txid:0]
[]WARNING:  terminating connection because of crash of another server
process
2012-07-13 17:06:19.895 MSK 67435 pgsql@pgsql from [local] [vxid:2/0 txid:0]
[]DETAIL:  The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
2012-07-13 17:06:19.895 MSK 67435 pgsql@pgsql from [local] [vxid:2/0 txid:0]
[]HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
2012-07-13 17:07:27.072 MSK 68607 @ from  [vxid: txid:0] []HINT:  If this
has occurred more than once some data might be corrupted and you might need
to choose an earlier recovery target.


Is that something which was fixed=20
already?

PS: update to 9.0.8 planned on next week.

Re: BUG #6736: Hot-standby replica crashed after failover:

От
Simon Riggs
Дата:
On 13 July 2012 14:38,  <maxim.boguk@gmail.com> wrote:

> 2012-07-13 17:06:19.732 MSK 79724 @ from  [vxid:1/0 txid:0] []PANIC:  WAL
> contains references to invalid pages

The problem is not connected with Hot Standby. The issue relates to
index code that contains problems, leaving invalid pages. These are
not reported until end of recovery. That has now been changed to be
reported earlier, so its clearer that this situation exists.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services