Hi, In current SR, since a backup history file is not replicated, the standby always starts an archive recovery without a backup history file, and a wrong minRecoveryPoint might be used. This is not a problem for SR itself, but would cause trouble when SR cooperates with Hot Standby.
HS begins accepting read-only queries after a recovery reaches minRecoveryPoint (i.e., a database has become consistent). So, a wrong minRecoveryPoint would execute read-only queries on an inconsistent database. A backup history file should be replicated at the beginning of the standby's recovery. This problem should be addressed right now? Or, I should wait until current simple SR patch has been committed? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers