Re: DDL commands take forever

From: "Leonardo M(dot)" Ramé <l(dot)rame(at)griensu(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: DDL commands take forever
Date: 2009-12-29 20:24:43
Message-ID: 1262118283.3102.64.camel@leonardo-laptop
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

El mar, 29-12-2009 a las 15:05 -0500, Merlin Moncure escribió:
> > This solves the locking problem, but what happens to transactions? the
> > app is still working in transaction mode, or just applying changes after
> > every Insert/Update/Delete?.
>
> huh...the default transaction mode _is_ read committed :-).
>
> merlin
>

Merlin, knowning this, I'm asking to the developers of the connection
library because in their code, if I use the default connection mode,
then the transactions are ingnored, applying the changes immediately
after every Insert, Update or Delete.

--
Leonardo M. Ramé
Griensu S.A. - Medical IT Córdoba
Tel.: 0351-4247979

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Anthony 2009-12-29 20:41:21 memory usage of group by select
Previous Message akp geek 2009-12-29 20:21:18 Re: Comparing 2 databases