Repository navigation
Upset best practice? #420
Description
Hi,
I'm currently upserting around 2.5 million rows to Postgres. I replaced my previous use of Sqlalchemy + psycopg2 with Asyncpg, but I'm not seeing the performance gains I expected. I have a complex query statement that utilizes ON CONFLICT to upset. SQLalchemy has an ORM method for this, but I don't see anything equivalent in the Asyncpg docs. I currently use executemany and pass a list of tuples that were converted from a Pandas data frame. I don't think I would be able to perform my upset function using copy_records_to_table, can you advise on how to approach this with Asyncpg?
Activity
elprans commentedon Mar 22, 2019
#295 should boost the
executemany()manyfold. I'll try to find time to get it merged soon.pkeeper commentedon Jul 19, 2019
Please do.
We've chosen asyncpg for it's performance, and we have a lot of upserts, that are working hacky now.
elprans commentedon Nov 26, 2020
#295 has been merged,
executemanyperformance should be much better in the next release.