You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
So, the problem is not when no delimiter is specified, but when no options are provided at all.
COPY customer FROM '/Users/wanshenl/Desktop/data/tpch1/customer.tbl' with (FORMAT csv); should work (but fail correctly because dbgen output isn't comma-separated).
Postgres seems to default to CSV if no options are provided, we should probably do the same. Should be a trivial fix.
pmenon
changed the title
Crash in Parser when using COPY without DELIMITER
Crash in Parser when using COPY without options
Jun 12, 2018
COPY
got introduced in #1371, including parser changes. Not explicitly specifying a delimiter however crashes Peloton in the parser.Example from @lmwnshn:
postgres=# COPY customer FROM '/Users/wanshenl/Desktop/data/tpch1/customer.tbl';
Peloton output with stack trace
The text was updated successfully, but these errors were encountered: