Re: speed concerns with executemany()

On 12/23/2016 04:59 PM, Christophe Pettus wrote:
>
>> On Dec 23, 2016, at 16:58, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>> I understood it did:
>>
>> http://initd.org/psycopg/docs/usage.html#transactions-control
>>
>> "It is possible to set the connection in autocommit mode: this way all the commands executed will be immediately committed and no rollback is possible. A few commands (e.g. CREATE DATABASE, VACUUM...) require to be run outside any transaction: in order to be able to run these commands from Psycopg, the connection must be in autocommit mode: you can use the autocommit property (set_isolation_level() in older versions)."
>
> My somewhat garbled thought was that each of the component INSERTs in the .executemany would be getting its own transaction unless the connection was set to autocommit... but I'll admit I haven't tested it.

Don't you mean?:
My somewhat garbled thought was that each of the component INSERTs in
the .executemany would be getting its own transaction if the connection
was set to autocommit... but I'll admit I haven't tested it.

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

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com