"David F. Skoll" <dfs@xxxxxxxxxxxxxxxxxx> writes: > Sure enough: > Oct 27 14:26:35 colo2vs1 canit-failover-wal-archive[29118]: > Warning: rsync succeeded, but local_sha1 1fe9fc62b2a05d21530decac1c5442969adc5819 > != remote_sha1 4f9f8bcd151129db64acd05470f0f05954b56232 !! > This is a "can't happen" situation, so I have to investigate bugs in rsync, > ssh, the kernel, the network, the disk.... bleah. > But I'm pretty sure it's not a PostgreSQL problem. > (My script exits with non-zero status if the SHA1s mismatch, and PostgreSQL > re-archives the WAL a short time later, and that succeeds, so I'm happy > for now.) So, when it archives successfully the second time, which if either of the two mismatched sha1's proves to have been correct? (I'm still wondering about the possibility that the WAL file is changing underneath you ...) regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
