|From:||Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>|
|To:||Chris Travers <chris(dot)travers(at)gmail(dot)com>|
|Cc:||Vladimir Borodin <root(at)simply(dot)name>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Funny WAL corruption issue|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> I ran into a funny situation today regarding PostgreSQL replication and
> wal corruption and wanted to go over what I think happened and what I
> wonder about as a possible solution.
Sad story. Unfortunately I have no idea what could be a reason nor can I
suggest a good way to find it unless there is an already know sequence
of steps that reproduces an issue.
I just wanted to point out that a hardware issue or third party software
issues (bugs in FS, software RAID, ...) could not be fully excluded from
the list of suspects. According to the talk by Christophe Pettus 
it's not that uncommon as most people think.
If the issue reproduces from time to time on one replica and doesn't on
the second identical replica there is a good chance that you've faced a
hardware issue. Another thing that is worth checking is a SMART status
of the hard drive.
|Next Message||Sokolov Yura||2017-08-10 12:58:43||Re: Fix performance degradation of contended LWLock on NUMA|
|Previous Message||Chris Travers||2017-08-10 12:39:22||Re: Funny WAL corruption issue|