Re: [psycopg] speed concerns with executemany()
От | Adrian Klaver |
---|---|
Тема | Re: [psycopg] speed concerns with executemany() |
Дата | |
Msg-id | f5da7054-a8c8-05da-3ced-6913c26b3e17@aklaver.com обсуждение исходный текст |
Ответ на | Re: [psycopg] speed concerns with executemany() (Christophe Pettus <xof@thebuild.com>) |
Ответы |
Re: [psycopg] speed concerns with executemany()
|
Список | psycopg |
On 12/23/2016 05:37 PM, Christophe Pettus wrote: > >> On Dec 23, 2016, at 17:23, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> Yet the data was available immediately in another session without a explicit COMMIT, so how is psycopg2 committing theINSERTs? > > autocommit = True means psycopg2 doesn't issue an initial BEGIN, so each INSERT commits when done (just like a top-levelpsql session)... thus "autocommit." Alright that I get. Still the practical outcome is each INSERT is being done in a transaction (an implicit one) so the transaction overhead comes into play. Or am I missing something? > > -- > -- Christophe Pettus > xof@thebuild.com > -- Adrian Klaver adrian.klaver@aklaver.com
В списке psycopg по дате отправления: