-
Notifications
You must be signed in to change notification settings - Fork 170
Ingest metric data with COPY to get better performance #1462
Conversation
f75178c
to
a42238a
Compare
a42238a
to
7fe0b84
Compare
Due to recent changes in the extension I needed to temporarily tweak |
e486765
to
47f919b
Compare
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.
The implementation looks good. We should have some end-to-end test, that can stimulate normal COPY ingest and with conflict.
@Harkishen-Singh There are existing e2e tests for testing various duplicate scenarios (check |
8665cc0
to
ce0c08a
Compare
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.
Minor nit, looks good otherwise 🎉
7e93d98
to
9cb1b3f
Compare
We try COPY into metric table. If there is a conflict situation (eg. duplicate key violation) we catch it on client and retry by COPYing to temporary table and doing ON CONFLICT insert from there. Prevent using old extension branch as docker image - I will revert this before merge
9cb1b3f
to
38747c0
Compare
We try COPY into metric table. If there is a conflict situation
(eg. duplicate key violation) we catch it on client and retry
by COPYing to temporary table and doing ON CONFLICT insert from there.