pg_backup_start fails on standby when full_page_writes are disabled on primary

[Travis Ward <Travis.Ward@xxxxxxxxxxxx>]

I'm encountering the following error on the streaming standby after disabling full_page_writes on the primary database.

select pg_backup_start('Is this risky');

ERROR:  WAL generated with full_page_writes=off was replayed since last restartpoint

HINT: 

This means that the backup being taken on the standby is corrupt and

should not be used. Enable full_page_writes and run CHECKPOINT on the

primary, and then try an online backup again.

Given that both my primary and standby databases are located on a ZFS file system, which provides its own data integrity mechanisms, does the full_page_writes=off error from pg_backup_start indicate a real risk of corruption in the standby database, or is the error message inapplicable in a ZFS environment?"

Environment information

PostgreSQL version: 16

primary_conninfo: configured with connection to primary

restore_command: configured to restore wal-file 

Thanks,

Travis Ward