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

fix: fixed COPY restoration statement string #180

Merged
merged 1 commit into from
Aug 24, 2024

Conversation

wwoytenko
Copy link
Contributor

@wwoytenko wwoytenko commented Aug 24, 2024

Fixed TOC entry COPY restoration statement - added missing new line and semicolon. Now backward pg_dump call pg_restore 1724504511561 --file 1724504511561.sql` is backward compatible and works as expected

Closes #179

@wwoytenko wwoytenko added the bug Something isn't working label Aug 24, 2024
@wwoytenko wwoytenko added this to the v0.2b2 milestone Aug 24, 2024
@wwoytenko wwoytenko self-assigned this Aug 24, 2024
@wwoytenko wwoytenko merged commit 80cb1cc into main Aug 24, 2024
15 checks passed
@wwoytenko wwoytenko deleted the fix/data_entry_copy_stmt_fix branch August 30, 2024 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Converting dump into SQL results in missing semicolon and newline after FROM stdin
1 participant