Re: [psycopg] speed concerns with executemany() - Mailing list psycopg

From Daniele Varrazzo
Subject Re: [psycopg] speed concerns with executemany()
Date
Msg-id CA+mi_8bRFzam87VLPtqxmF=a8tt5=0RgH6-sK+w1Ae7Yujs4uA@mail.gmail.com
Whole thread Raw
In response to Re: [psycopg] speed concerns with executemany()  (Christophe Pettus <xof@thebuild.com>)
Responses Re: [psycopg] speed concerns with executemany()  (Adrian Klaver <adrian.klaver@aklaver.com>)
List psycopg
On Sat, Dec 24, 2016 at 1:09 AM, Christophe Pettus <xof@thebuild.com> wrote:
> Are you running with the transaction isolation level set to ISOLATION_LEVEL_AUTOCOMMIT?  If so, each of those INSERTs
willbe in its own transaction, and thus will go through the COMMIT overhead.  That by itself wouldn't explain a jump
thatlarge (in most environments), but it will definitely be *much* slower. 

Why do you say this? Psycopg doesn't wrap statements in BEGIN/COMMIT
when in autocommit mode. Are you referring about some implicit
transaction created by the database?

-- Daniele


psycopg by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: [psycopg] speed concerns with executemany()
Next
From: Adrian Klaver
Date:
Subject: Re: [psycopg] speed concerns with executemany()