On Fri, Jun 11, 2010 at 9:32 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Hmm, right now it doesn't even reconnect when it sees a corrupt record > streamed from the master. It's really pointless to retry in that case, > reapplying the exact same piece of WAL surely won't work. I think it should > disconnect, and then retry reading from archive and pg_xlog, and then retry > streaming again. That's pretty hopeless too, but it's at least theoretically > possible that something went wrong in the transmission and the file in the > archive is fine.
Yep, this makes more sense. 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
