Re: Table lock while adding a column and clients are logged in

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Table lock while adding a column and clients are logged in
Date: 2011-04-03 09:17:18
Message-ID: FD822692-15E2-40BC-824E-DE07ACF8D013@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 with the SELECT.

Sorry, but you're wrong about that. A statement that implicitly starts a transaction also implicitly COMMITs it. Otherwise single 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!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2011-04-03 09:22:10 Re: Table lock while adding a column and clients are logged in
Previous Message Darren Duncan 2011-04-03 06:21:18 Re: Postgres 9.1 - Release Theme