On Thu, Dec 3, 2020 at 12:14 PM osumi.takamichi@fujitsu.com
<osumi.takamichi@fujitsu.com> wrote:
>
> Hello
>
>
> I've made a new patch v05 that took in comments
> to filter out WALs more strictly and addressed some minor fixes
> that were discussed within past few days.
> Also, I changed the documentations, considering those modifications.
>
From a backup management tool perspective, how can they detect that
wal_level has been changed to ‘none' (and back to the normal)? IIUC
once we changed wal_level to none, old backups that are taken before
setting to ‘none’ can be used only for restoring the database to the
point before the LSN where setting 'wal_level = none'. The users can
neither restore the database to any points in the term of 'wal_level =
none' nor use an old backup to restore the database to the point after
LSN where setting 'wal_level = none’. I think we might need to provide
a way to detect the changes other than reading XLOG_PARAMETER_CHANGE.
Regards,
--
Masahiko Sawada
EnterpriseDB: https://www.enterprisedb.com/
