Understanding autocommit

From: Chris Angelico <rosuav(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Understanding autocommit
Date: 2012-08-22 08:33:25
Message-ID: CAPTjJmqkSabVm09wuMy_71KEsM3ekZRv+=Hn48Sj=xRG5oPG+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm looking at these two pages:

http://www.postgresql.org/docs/9.1/static/ecpg-sql-set-autocommit.html
http://www.postgresql.org/docs/9.1/static/sql-start-transaction.html

According to the first page, autocommit is off by default for
"embedded SQL programs". Does this mean everything except the 'psql'
command line interpreter, or is that some special case, and most
programs default to autocommit on?

Currently, I have explicit 'begin' statements in all our code. What
I'd like to achieve is DB2-style semantics where a transaction is
automatically and implicitly opened as soon as any query is performed,
and that transaction remains until committed or rolled back (or until
end of session implicit rollback).

I'm sure there's something really obvious here, but... how do I find
out whether my program's running in autocommit mode or not?

Thanks!

Chris Angelico

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2012-08-22 08:52:08 Re: Understanding autocommit
Previous Message Craig Ringer 2012-08-22 05:15:49 Re: Amazon High I/O instances