When a PostgreSQL connection is opened, a transaction is started before the previous transaction commits.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Just connect to a postgresql server with luadbi
2. PostgreSQL generates a warning "there is already a transaction in progress"

What is the expected output? What do you see instead?

I would see nothing if there is no such issue.

Please provide any additional information below.

I made a patch and commited on a new branch named 'postgres-fix'.
The new branch is in a cloned repository found on 
http://code.google.com/p/luadbi/source/clones

Original issue reported on code.google.com by crockabiscuit@gmail.com on 17 Oct 2012 at 1:36

[GoogleCodeExporter]

Hi! Apologies for the really slow response. I've just set up notifications to 
make sure I can stay on top of issues here in the future.

A similar issue was fixed in this commit: 
http://code.google.com/p/luadbi/source/detail?r=aab3ed7d93fe9b10b75e302c78773799
9a8b4a5f

It looks like your fix is different. Did you test with the above commit? or is 
it definitely a separate issue?

Original comment by MWild1 on 26 Apr 2013 at 12:17

[GoogleCodeExporter]

Original comment by MWild1 on 26 Apr 2013 at 12:22

• Added labels: Milestone-0.6

[GoogleCodeExporter]

The steps to reproduce this problem aren't exactly as described in the issue. 
To get luadbi to output that message, you have to try to BEGIN your own 
transaction.
As MWild1 points out, there is already a fix for this. Just turn on autocommit 
after connecting. With autocommit on, you'll get to be the master of your own 
transactions.

Original comment by david.or...@gmail.com on 24 May 2013 at 10:27

[GoogleCodeExporter]

I also believe this is already fixed.

Original comment by crockabiscuit@gmail.com on 24 May 2013 at 9:35

[GoogleCodeExporter]

Closing, as you believe this to be fixed.

Original comment by MWild1 on 29 Jul 2014 at 1:06

• Changed state: Fixed