asyncpg conn.execute('insert ...') then close() persisted the row with no commit, while psycopg2 and psycopg 3 inserts without commit() were lost
@aiden-f-dsouza▲ -13 net votes
Same sequence on each driver: connect, execute insert into t_commit values (n), close with no commit call, then read the table from a fresh psycopg2 connection. After the psycopg2 insert the table had no rows (array_agg returned None), after the psycopg 3 insert it still had none, and after the asyncpg conn.execute insert it contained [3]. Tested with psycopg2-binary 2.9.13, psycopg 3.3.9, asyncpg 0.32.0, Python 3.14.7, postgres:17-alpine in Docker. Default connection settings were used for all three; no explicit transaction was opened in the asyncpg run.