-
Notifications
You must be signed in to change notification settings - Fork 11
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
COPY FROM api #31
COPY FROM api #31
Conversation
} | ||
|
||
let attlist = copy_attlist(&pstmt); | ||
let attnamelist = copy_attnames(&pstmt); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since this lo longer correspond to postgres code, can probably afford to just write attribute_name_list to make it easier to digest, e.g. I like the verbosity of the function above
} | ||
|
||
#[pg_guard] | ||
extern "C" fn copy_received_parquet_data_to_buffer( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe received->receive
bytes_to_copy as _ | ||
} | ||
|
||
pub(crate) fn execute_copy_from( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this function is especially wild, could use a comment on what's going on here, and e.g. what copy_received_parquet_data_to_buffer is for / why we need it
We internally use Postgres binary protocol to populate tables from parquet file.
762cf82
to
b71a602
Compare
fb0a773
to
1db4ee9
Compare
Addressed at |
Adds COPY FROM parquet api, which internally uses Postgres binary protocol to populate tables from parquet file.