4 Commits
Author SHA1 Message Date
CI d785af82d5 Bump version to 0.1.0-RC.2 [skip ci] 2026-11-10 13:18:37 +00:00
james.maes 774482da5e Merge pull request 'fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only (release/0.1)' (#9) from fix/aurora-full-page-writes-0.1 into release/0.1
maven / build (push) Successful in 18m46s
build / maven (push) Successful in 18m46s
2026-11-10 13:00:02 +00:00
james.maesandClaude Fable 5.2 af5728a165 fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only
maven / build (push) Successful in 24m0s
build / maven (push) Successful in 24m0s
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:10 -06:00
CI e45f696da7 Bump version to 0.1.0-RC.1 [skip ci] 2026-11-06 19:12:55 +00:00
+5 -5
View File
@@ -18,20 +18,20 @@
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<properties>
<revision>0.5.0-SNAPSHOT</revision>
<revision>0.1.0-RC.2</revision>
<maven.compiler.source>21</maven.compiler.source>
<maven.compiler.target>21</maven.compiler.target>
<jacoco.version>0.8.15</jacoco.version>
<!-- QQQ Core 4.1.0-RC.22 from the Gitea registry, imported through qqq-bom-pom. It includes the after-rollback callbacks Collaboration needs. -->
<qqq.version>4.1.0-RC.26</qqq.version>
<qqq.version>4.1.0-RC.22</qqq.version>
<!-- Released Collaboration carrying the attachment lifecycle SPI. -->
<qbit-collaboration.version>1.2.0-RC.1</qbit-collaboration.version>
<qbit-collaboration.version>1.0.0</qbit-collaboration.version>
</properties>
<parent>
<groupId>com.kingsrook</groupId>
<artifactId>qbit-build-parent</artifactId>
<version>2.2.1</version>
<version>2.1.1</version>
</parent>
<groupId>com.kingsrook.qbits</groupId>
@@ -236,7 +236,7 @@
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<qqq.snapshot.version>4.1.0-RC.26</qqq.snapshot.version>
<qqq.snapshot.version>${qqq.version}</qqq.snapshot.version>
</properties>
<dependencyManagement>
<dependencies>