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

Converting dump into SQL results in missing semicolon and newline after FROM stdin #179

Closed
wnatrifork opened this issue Aug 24, 2024 · 2 comments · Fixed by #180
Closed
Assignees
Labels
bug Something isn't working

Comments

@wnatrifork
Copy link

Converting a dump into SQL file:

pg_restore 1724504511561 --file 1724504511561.sql

Note that semicolon and newline is missing after FROM stdin

--
-- Data for Name: "backlog_entry"; Type: TABLE DATA; Schema: "public"; Owner: "wna"
--

COPY "public"."backlog_entry" ("unique_id", "created", "year", "month", "department_id", "source") FROM stdin33cd6668-6dd7-4059-95a1-e5ae03027c04	2020-05-25 08:22:27.177641	2020	4	205e604f-14e4-4073-ab7f-886515ec4eea	recurring

Dumping database with pg_dump does not have this issue:

% pg_dump bireporting --format=d --file=bireporting
% pg_restore bireporting --file bireporting.sql
--
-- Data for Name: backlog_entry; Type: TABLE DATA; Schema: public; Owner: wna
--

COPY public.backlog_entry (unique_id, created, year, month, department_id, source) FROM stdin;
33cd6668-6dd7-4059-95a1-e5ae03027c04	2020-05-25 08:22:27.177641	2020	4	205e604f-14e4-4073-ab7f-886515ec4eea	recurring
@wwoytenko wwoytenko self-assigned this Aug 24, 2024
@wwoytenko
Copy link
Contributor

Thank you for reporting this. I've double-checked, and it seems you're correct. I will fix it.

@wwoytenko
Copy link
Contributor

FIxed in #180

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 a pull request may close this issue.

2 participants