james.maesandClaude Fable 5.2
0d989683eb
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>
1.7 KiB
1.7 KiB
Known issues and unfinished work
Updated: 2026-11-06. These are unresolved items carried into the first release candidate, not a plan currently being executed.
- Public Collaboration 0.1.0-RC.6 does not provide the attachment lifecycle, upload journal, recovery and download APIs this module requires.
- The corresponding canonical Collaboration integration is Collaboration PR 59 (
kof22/collab-v2), not yet published. It requires confirmed rollback callbacks in QQQ Core/RDBMS; public QQQ 4.1.0-RC.21 is insufficient for that dependency chain. qbit-collaboration.versionis still0.1.0-SNAPSHOT, a placeholder for source integration. The release candidate must pin a published Collaboration RC beforerelease/0.1is pushed (see RELEASE-STATUS.md). No clean consumer installation of the complete public cohort has been demonstrated.- Full Record Files verification, database integration, retained-file recovery and final standard-UI acceptance remain incomplete for this reconciled source.
- Permanent access depends on the host's durable object storage, backups, retention and permission configuration. A source-level interface or unit test alone does not prove operational permanence.
- The Amazon Aurora PostgreSQL rule (
full_page_writes = offaccepted on Aurora only) is tested on stock PostgreSQL 17 with Aurora simulated by a test-onlyaurora_version()function. No test in this repository runs against a real Aurora cluster, and the opt-in PostgreSQL suites do not run in the shared CI build. The detection resolvesaurora_version()through the sessionsearch_path, so a role that can create functions in a schema on that path of a stock PostgreSQL database could make it report Aurora; the application role must not hold that privilege.