Files
james.maesandClaude Fable 5.2 0d989683eb
maven / build (push) Successful in 9m12s
build / maven (push) Successful in 9m12s
fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only
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

4.5 KiB

Changelog

All notable changes are documented here, following Keep a Changelog and semantic versioning. Record Files is pre-1.0: a 0.1.0-RC.N release candidate is a published, immutable artifact, not a production 1.0 claim (see docs/RELEASE-STATUS.md).

[Unreleased]

Changed

  • PostgreSQL qualification (RecordFilesPostgres) accepts full_page_writes = off when, and only when, the server is Amazon Aurora PostgreSQL. Aurora reports full_page_writes = off (measured on engine 17.9) and the parameter is not in its 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. Before this change Record Files refused every Aurora PostgreSQL database with its "exact writable PostgreSQL 17 database" message. Aurora is detected inside the existing settings query with to_regprocedure('aurora_version()') IS NOT NULL, which returns false and never raises on stock PostgreSQL. Nothing else is relaxed: stock PostgreSQL with full_page_writes = off is still refused, and on Aurora fsync = on, synchronous_commit of on or remote_apply, a writable primary, PostgreSQL 17, a UTC session, READ COMMITTED, a lock_timeout from 1 to 5000 ms and every owner-table check are required exactly as before. Covered by PostgresDurabilityRuleTest (every build) and PostgresAuroraQualificationTest (opt-in, real PostgreSQL 17, Aurora simulated by a test-only aurora_version() function).

[0.1.0-RC.1] - 2026-11-06

Planned as 0.1.0-RC.1, the first artifact published from this repository. It is published by pushing develop to release/0.1; the shared KofTwentyTwo/ci-workflows Maven workflow computes the 0.1.0-RC.N version, deploys to the Gitea Maven registry (https://git.kof22.com/api/packages/QRun-IO/maven) and tags v0.1.0-RC.N. Nothing is published from develop except the 0.1.0-SNAPSHOT.

Added

  • First published release candidate of the standalone QBit extracted from Website-Backend b6fb2382: retained files, ordered collections, review vocabulary, append-only audit, resumable upload sessions, tracked downloads, archive-and-delete, verified print observations, and the tests classifier with the public integration fixtures.
  • CHANGELOG.md, and a release-status document that records the publication path, the dependency cohort and the Forge development pin this release replaces.
  • Test-only PostgreSQL fixture diagnostics from the GG Forge qualification (record-files-postgres-diagnostics, record-files-linux-fixture): POSTGRES_FIXTURE_HEALTH container observation after each PostgreSQL intake case, and FixtureEndpoint, which resolves the disposable container's reachable host and published port (honouring TESTCONTAINERS_HOST_OVERRIDE, with the sibling bridge address for a JVM inside a build container) instead of hard-coding 127.0.0.1. This is what lets the suite run on the shared container-build runners.

Changed

  • Archive capture (ArchiveSecurity.digest) now tolerates host table customizers that run only on insert, update or delete (PRE_/POST_INSERT_RECORD, PRE_/POST_UPDATE_RECORD, PRE_/POST_DELETE_RECORD), since they cannot change what a reader may see. Query, get and personalization customizers still refuse the capture with "Archive capture does not support this table's custom visibility policy." This is the source form of the change that GG Forge carried as the -archive1 suffix of its development pin 0.1.0-forge.162af9a7b8cd-archive1; it was recovered from that artifact's bytecode and is covered by ArchiveTest.mutationCustomizersAreToleratedWhileVisibilityCustomizersRefuseCapture.
  • .gitea/ is no longer ignored, so the shared CI caller (.gitea/workflows/build.yaml, PR 2) is tracked normally; the retired platform-ci caller in docs/release/qrun-release.reference.yaml is marked superseded.

Known limits carried into the release candidate

  • The build needs a Collaboration artifact that carries the attachment lifecycle, upload journal and download SPI (Collaboration PR 59). Public Collaboration 0.1.0-RC.6 does not have it, and the qbit-collaboration.version property still names 0.1.0-SNAPSHOT; pin the published Collaboration release candidate before pushing release/0.1.
  • Everything in docs/KNOWN-ISSUES.md still applies: no malware scanning, no WORM proof, PostgreSQL script unqualified for production, no complete public-cohort consumer installation yet.