Comment by philjohn
1 month ago
If you're doing large batch inserts, I've found using the COPY INTO the fastest way, especially if you use the binary data format so there's no overhead on the postgres server side.
1 month ago
If you're doing large batch inserts, I've found using the COPY INTO the fastest way, especially if you use the binary data format so there's no overhead on the postgres server side.
That doesn't work well with conflicts tho iirc
COPY INTO a temp table and INSERT INTO... SELECT FROM... ON CONFLICT UPDATE...