I finally got permission to patch a highly used db from 9.0.15 to .17. Is there any way to know if the WAL replay issue has effected the standby? I don't have the reported bloat, is that THE test? Is there any way to measure the current state of this issue listed in the 9.0.16 release notes:
Fix possible mis-replay of WAL records when some segments of a relation aren't full size (Greg Stark, Tom Lane)
The WAL update could be applied to the wrong page, potentially many pages past where it should have been. Aside from corrupting data, this error has been observed to result in significant "bloat" of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode does not appear to be a significant risk during crash recovery, only when initially synchronizing a standby created from a base backup taken from a quickly-changing master.
