Update aurora-dsql-connectors to v0.2.0#2
Open
amaksimo wants to merge 4 commits into
Open
Conversation
Add support for Amazon Aurora DSQL as a storage engine for OpenFGA. - Add DSQL-specific migrations adapted for DSQL constraints (ASYNC index creation, NO TRANSACTION DDL, epoch-based goose table IDs, full indexes instead of partial) - Add OCC retry logic with exponential backoff for write operations - Skip FOR UPDATE clause (DSQL uses OCC at commit time) - Use aurora-dsql-connectors/go/pgx for IAM authentication - Optimize query plans to avoid table scans on DSQL - Respect OPENFGA_DATASTORE_USERNAME for DSQL connections - Add DSQL migration tooling and test fixtures
feat: add Aurora DSQL storage backend
Pool config fields (MaxConns, MinConns, MaxConnLifetime, MaxConnIdleTime) were removed from dsql.Config in v0.2.0. Pass them via a separate pgxpool.Config to dsql.NewPool instead.
Benjscho
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aurora-dsql-connectors/go/pgxfrom v0.1.2 to v0.2.0MaxConns,MinConns,MaxConnLifetime,MaxConnIdleTime) were removed fromdsql.Configin v0.2.0; pass them via a separatepgxpool.Configtodsql.NewPoolinsteadConnector changelog (v0.1.2 → v0.2.0)
v0.2.0 — Breaking: pool config via pgxpool.Config
dsql.Config(MaxConns,MinConns,MaxConnLifetime,MaxConnIdleTime,HealthCheckPeriod)NewPoolnow accepts an optional*pgxpool.Configparameter, exposing the full pgxpool configuration surface directlyMaxConnLifetimeJitter, all pool connections expire simultaneously causing a thundering herd of reconnections requiring IAM token generationNewPool(ctx, config)still applies DSQL defaults (55min lifetime, 10min idle)NewPool(ctx, config, poolCfg)gives full control over pool settingsBeforeConnectcallbacks are chained (user callbacks run first, then IAM token injection)v0.1.3 — Token cache removal
TokenCachefield andClearTokenCache()method were removed fromPoolFull upstream changelog: awslabs/aurora-dsql-connectors@go/pgx/v0.1.2...go/pgx/v0.2.0
Test plan
go build ./...)