fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only #8

Merged

james.maes merged 1 commits from fix/aurora-full-page-writes-develop into develop

2026-11-10 15:31:15 +00:00

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	0d989683eb	fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only maven / build (push) Successful in 9m12s Details build / maven (push) Successful in 9m12s Details RecordFilesPostgres refused every Amazon Aurora PostgreSQL database: Aurora reports full_page_writes = off (measured on engine 17.9) and the parameter is not in the cluster parameter group, so it cannot be changed. Its storage layer does not write torn pages, so the protection that setting gives stock PostgreSQL is not needed there. The settings query now carries a twelfth column, to_regprocedure('aurora_version()') IS NOT NULL, which is true on Aurora and false on stock PostgreSQL without raising. full_page_writes = off is accepted only when that column is true. Stock PostgreSQL with full_page_writes = off is still refused, and fsync, synchronous_commit, the writable primary, version, UTC, READ COMMITTED, the lock_timeout bound and every owner-table check are unchanged on both. Tests: PostgresDurabilityRuleTest (pure rule, every build) and PostgresAuroraQualificationTest (opt-in, real PostgreSQL 17, Aurora simulated by a test-only aurora_version() function and ALTER SYSTEM full_page_writes). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-09 20:29:19 -06:00

Author

SHA1

Message

Date

james.maesandClaude Fable 5.2

0d989683eb

fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only

maven / build (push) Successful in 9m12s

Details

build / maven (push) Successful in 9m12s

Details

RecordFilesPostgres refused every Amazon Aurora PostgreSQL database: Aurora
reports full_page_writes = off (measured on engine 17.9) and the parameter is
not in the cluster parameter group, so it cannot be changed. Its storage layer
does not write torn pages, so the protection that setting gives stock
PostgreSQL is not needed there.

The settings query now carries a twelfth column,
to_regprocedure('aurora_version()') IS NOT NULL, which is true on Aurora and
false on stock PostgreSQL without raising. full_page_writes = off is accepted
only when that column is true. Stock PostgreSQL with full_page_writes = off is
still refused, and fsync, synchronous_commit, the writable primary, version,
UTC, READ COMMITTED, the lock_timeout bound and every owner-table check are
unchanged on both.

Tests: PostgresDurabilityRuleTest (pure rule, every build) and
PostgresAuroraQualificationTest (opt-in, real PostgreSQL 17, Aurora simulated
by a test-only aurora_version() function and ALTER SYSTEM full_page_writes).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

2026-11-09 20:29:19 -06:00