THE BAD NEWS:
If your site uses Postgres' streaming replication to create a
read-only hot-standby, such as for reporting or to support search
capacity needs, this message is for you.
On Nov, 18, a bug was reported to the Postgres hackers list that can
cause extreme corruption of hot-standby
UPDATE
I need clarify and correct the information below: this is not
restricted streaming-replication based hot-standby replicas, it is for
all hot_standby-enabled replicas (regardless of the mechanism used to
ship the WAL data) when there is a recovery.conf in place. This is
per:
