Btrfs Snapshot Rollback and Pacman Database Synchronization

Arch Linux users utilizing Btrfs subvolumes often rely on snapshots to revert the system state after a failed update. While tools like Timeshift can restore the root subvolume to a previous state, the synchronization between the filesystem state and the Pacman package database requires careful consideration.

The primary constraint is that the Pacman database resides within the root subvolume. If a rollback restores the binaries and the database to a previous version, but external configuration changes or partial updates occurred in non-snapshotted areas, a discrepancy may emerge between the expected package versions and the actual system state.

• Does a Btrfs snapshot restore inherently guarantee that the Pacman database is perfectly synchronized with the restored binaries?
• What is the expected behavior when rolling back a system state that includes a kernel update while maintaining a separate, non-snapshotted /boot partition?