>I think it's also important to suggest to the users how they can turn
>on hot_standby on their standby. So, perhaps-a-bit-verbose hint would
>be like this.
>"Either start this standby from base backup taken after setting
>wal_level to \"replica\" on the primary, or turn off hot_standby
>here."
>Th
At Fri, 15 Jan 2021 17:04:19 +0800, "lchch1...@sina.cn"
wrote in
>
> >Mmm. Maybe something's missing. If you took the base-backup using
> >pg_basebackup, that means max_wal_senders > 0 on the primary. If you
> >lowered wal_level in the backup (or replica) then started it, You
> >would get somet
>Mmm. Maybe something's missing. If you took the base-backup using
>pg_basebackup, that means max_wal_senders > 0 on the primary. If you
>lowered wal_level in the backup (or replica) then started it, You
>would get something like this.
>| FATAL: WAL streaming (max_wal_senders > 0) requires wal_lev
At Fri, 15 Jan 2021 15:32:58 +0800, "lchch1...@sina.cn"
wrote in
>
> Sorry, I don't known why it showed in wrong format, and try to correct it.
> -
>
> When I do PITR in a strange step, I get this FATAL:
>
> 2021-01-15 15:02:52.364 CST [14958] FATAL: hot standby is not possible
> becaus
Sorry, I don't known why it showed in wrong format, and try to correct it.
-
When I do PITR in a strange step, I get this FATAL:
2021-01-15 15:02:52.364 CST [14958] FATAL: hot standby is not possible because
wal_level was not set to "replica" or higher on the primary server
2021-01-15 15:0
Hello hackers,
When I do PITR in a strange step, I get this FATAL:
2021-01-15 15:02:52.364 CST [14958] FATAL: hot standby is not possible because
wal_level was not set to "replica" or higher on the primary server2021-01-15
15:02:52.364 CST [14958] HINT: Either set wal_level to "replica" on the
