Re: speed concerns with executemany()

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, mike bayer <mike_mp(at)zzzcomputing(dot)com>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org>
Subject: Re: speed concerns with executemany()
Date: 2016-12-24 01:37:28
Message-ID: EB1F8C89-4106-43BB-AB42-A6665F22B07D@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg


> On Dec 23, 2016, at 17:23, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> Yet the data was available immediately in another session without a explicit COMMIT, so how is psycopg2 committing the INSERTs?

autocommit = True means psycopg2 doesn't issue an initial BEGIN, so each INSERT commits when done (just like a top-level psql session)... thus "autocommit."

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Adrian Klaver 2016-12-24 02:55:40 Re: speed concerns with executemany()
Previous Message Adrian Klaver 2016-12-24 01:23:21 Re: speed concerns with executemany()