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.

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

sync after unroll #620

Merged
merged 1 commit into from
Feb 10, 2022
Merged

sync after unroll #620

merged 1 commit into from
Feb 10, 2022

Conversation

tpolecat
Copy link
Member

@tpolecat tpolecat commented Feb 9, 2022

Per the doc:

At completion of each series of extended-query messages, the frontend should issue a Sync message. This parameterless message causes the backend to close the current transaction if it's not inside a BEGIN/COMMIT transaction block ("close" meaning to commit if no error, or roll back if error). Then a ReadyForQuery response is issued.

Not doing this can lead to weird behavior if you try to do things on the session after executing a portal (async notifications are stopped, for example).

@tpolecat tpolecat merged commit cf6bb04 into main Feb 10, 2022
@tpolecat tpolecat deleted the extended-sync branch February 10, 2022 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant