Repository navigation
PostgreSQL: Rolling back a failed transaction with COPY results in expecting ParseComplete but received CommandComplete #3139
Description
Bug Description
When
- using
copy_out_raw - which has a runtime failure
- which runs inside a transaction
- when the tx is rolled back
- the main connection is no longer usable due to a protocol error
Minimal Reproduction
this PR has the testcase which reproduces my error, as well as a tentative solution for a fix.
Info
- SQLx version: 0.8.0-alpha.0
- SQLx features enabled: postgres, runtime-tokio
- Database server and version: PostgreSQL 16.2
- Operating system: Ubuntu 22.04 x86_64
rustc --version: 1.77.0-beta.9
Activity
[-]Rolling back a failed subtransaction with COPY results in `expecting ParseComplete but received CommandComplete`[/-][+]PostgreSQL: Rolling back a failed subtransaction with COPY results in `expecting ParseComplete but received CommandComplete`[/+][-]PostgreSQL: Rolling back a failed subtransaction with COPY results in `expecting ParseComplete but received CommandComplete`[/-][+]PostgreSQL: Rolling back a failed transaction with COPY results in `expecting ParseComplete but received CommandComplete`[/+]abonander commentedon Apr 19, 2024
fixed by #3138 (?)