Re: Is autocommit=true bad?

From: Alex Satrapa <alex(at)lintelsys(dot)com(dot)au>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Is autocommit=true bad?
Date: 2004-01-27 23:26:49
Message-ID: 4016F3B9.5020403@lintelsys.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Net Llama! wrote:
> At any rate, are there any negative consequences to setting setting
> autocommit=true, such as performance hits (and the obvios filling up
> diskspace because of the logging)?

The greatest negative consequence will be that the code obviously isn't
doing what the programmers think it's doing. The log entry is occuring
because someone is issuing a COMMIT somewhere - obviously expecting that
they're in a transaction at that point.

Check the code, and consider turning autocommit off if it looks like you
need a transaction over more than one statement.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message William Harazim 2004-01-28 00:06:09 Manually authenticating users in pg_shadow
Previous Message Net Llama! 2004-01-27 22:58:35 Is autocommit=true bad?