Re: Table lock while adding a column and clients are logged in - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Table lock while adding a column and clients are logged in
Date
Msg-id FD822692-15E2-40BC-824E-DE07ACF8D013@solfertje.student.utwente.nl
Whole thread Raw
In response to Re: Table lock while adding a column and clients are logged in  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Table lock while adding a column and clients are logged in
List pgsql-general
On 2 Apr 2011, at 12:44, Thomas Kellerer wrote:

> Even after a plain SELECT you should issue a COMMIT (or ROLLBACK) to end the transaction that was implicitely started
withthe SELECT. 


Sorry, but you're wrong about that. A statement that implicitly starts a transaction also implicitly COMMITs it.
Otherwisesingle UPDATE and INSERT statements outside of transaction blocks would not COMMIT, and they do. 

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,4d983b2f651341263218540!



pgsql-general by date:

Previous
From: Darren Duncan
Date:
Subject: Re: Postgres 9.1 - Release Theme
Next
From: Alban Hertroys
Date:
Subject: Re: Table lock while adding a column and clients are logged in