Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PostgreSQL Bugfix: Ensure connection is usable after failed COPY inside a transaction #3138

Merged
merged 2 commits into from
Apr 19, 2024
Merged

PostgreSQL Bugfix: Ensure connection is usable after failed COPY inside a transaction #3138

merged 2 commits into from
Apr 19, 2024

Commits on Apr 4, 2024

  1. Include test case for regular subtransactions 

    While using COPY and subtransactions I kept running into errors.
This test case documents that error, it currently fails with:

    Error: encountered unexpected or invalid data: expecting ParseComplete but received CommandComplete
    @feikesteenbergen
    feikesteenbergen committed Apr 4, 2024
    Configuration menu
    Copy the full SHA
    e920682 View commit details
    Browse the repository at this point in the history

  2. PostgreSQL Copy: Consume ReadyForQuery on error 

    When a COPY statement was in error inside a subtransaction,
a Protocol Error used to be raised. By consuming the ReadyForQuery
message when there is an error, we no longer have this issue.
    @feikesteenbergen
    feikesteenbergen committed Apr 4, 2024
    Configuration menu
    Copy the full SHA
    70c1876 View commit details
    Browse the repository at this point in the history