On Nov 19, 2013, at 4:05 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> Hi,
>
> On 2013-11-19 15:53:36 -0800, Christophe Pettus wrote:
>> From my understanding, the problem only occurs over streaming
>> replication; if the secondary was never a hot standby, and only used
>> the archived WAL segments, that would be safe. Is that correct?
>
> Not entirely.
>
> It's related to a standby running with hot_standby=on. Both archive
> based and streaming replication can be used with hot_standby=on or off.
>
So, does that mean that restoring from PITR based backups from tools like barman and wal-e could exhibit the same issue
ifhot_standby=on was in the postgresql.conf?
