pgsql: Revert "Mark modified the FSM buffer as dirty during recovery"

Revert "Mark modified the FSM buffer as dirty during recovery"

This reverts commit c06d1a4ba6b26eef27b04074683cccade6c277ee.

The commit assumed that if the FSM code tolerates torn pages, everything else
does so. Readers that do not tolerate that include RelationCopyStorage(),
used by ALTER TABLE ... SET TABLESPACE for every fork, the read stream in
RelationCopyStorageUsingBuffer() used by CREATE DATABASE ... STRATEGY =
wal_log, and, most awkwardly, the checksum verification in base backups and
pg_checksums.

Reported-by: Noah Misch <noah(at)leadboat(dot)com>
Discussion: https://postgr.es/m/20260901211837.f6.noahmisch%40microsoft.com
Backpatch-through: 14
Reviewed-by: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/d0518cb3e40503859e5dd17a0a75de9b8967fe4b

Modified Files
--------------
src/backend/storage/freespace/freespace.c | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)