superfly/corrosion

Bulletproof postgres transaction handling

Open

#502 opened on Aug 7, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (83 forks)auto 404
buggood first issue

Repository metrics

Stars
 (1,817 stars)
PR merge metrics
 (PR metrics pending)

Description

As per https://github.com/superfly/corrosion/pull/176 if an statement within an ongoing postgres transaction errors we should reject all commands other than a ROLLBACK. Currently we only do discard_until_sync on errors so if a transaction fails and the client sends a SYNC message then it can send another failing statement. Also as per the original PR we should error on trying to start an nested transaction.

Contributor guide

Research direction
Investigate how the PostgreSQL protocol handles transaction errors and the `discard until sync` mechanism. Review the referenced PR #176 for context. Identify where transaction state is managed and where nested transactions are allowed. Understand the test suite for transaction handling to add appropriate tests.
Tech stack
postgresqlrust
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70