Ezequias Rodrigues da Rocha wrote:
This is delphi. I don't intent you understand but the sql actions are quite
simple (I am reading a list of numbers).
Well, let's see - the last Pascal I did was in 1986 I think...
If not dm.database1.InTransaction then
dm.database1.StartTra
Ok you teach me. Thank you and sorry. :(
I just want to know why is it occuring. I am pretty sad.
Ezequias
2007/2/12, Reinoud van Leeuwen <[EMAIL PROTECTED]>:
On Mon, Feb 12, 2007 at 03:08:27PM -0300, Ezequias Rodrigues da Rocha
wrote:
> I mean really deadlock. Other transactions can't access
On Mon, Feb 12, 2007 at 03:08:27PM -0300, Ezequias Rodrigues da Rocha wrote:
> I mean really deadlock. Other transactions can't access the database until
> the main transaction is complete.
What you describe sounds like a blocking lock: one transaction uses a
resource and another has to wait unt
This is delphi. I don't intent you understand but the sql actions are quite
simple (I am reading a list of numbers).
If not dm.database1.InTransaction then
dm.database1.StartTransaction;
For i:= 0 to memo1.Lines.Count - 1 do
Begin
// Catching ID
On Mon, 2007-02-12 at 12:08, Ezequias Rodrigues da Rocha wrote:
> I mean really deadlock. Other transactions can't access the database
> until the main transaction is complete. A question:
>
> PostgreSQL doesn't permit multiple transactions concurrently ?
Again, that's not a deadlock. A deadlock
Ezequias Rodrigues da Rocha wrote:
2007/2/12, Richard Huxton :
Ezequias Rodrigues da Rocha wrote:
> I mean really deadlock. Other transactions can't access the database
until
> the main transaction is complete. A question:
>
> PostgreSQL doesn't permit multiple transactions concurrently ?
PG h
2007/2/12, Richard Huxton :
Ezequias Rodrigues da Rocha wrote:
> I mean really deadlock. Other transactions can't access the database
until
> the main transaction is complete. A question:
>
> PostgreSQL doesn't permit multiple transactions concurrently ?
PG has quite good concurrency behaviour.
Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> schrieb:
> I mean really deadlock. Other transactions can't access the database until the
> main transaction is complete. A question:
That's not true.
>
> PostgreSQL doesn't permit multiple transactions concurrently ?
Why not? Show us a complete
Ezequias Rodrigues da Rocha wrote:
I mean really deadlock. Other transactions can't access the database until
the main transaction is complete. A question:
PostgreSQL doesn't permit multiple transactions concurrently ?
PG has quite good concurrency behaviour. And "can't access the database"
i
I mean really deadlock. Other transactions can't access the database until
the main transaction is complete. A question:
PostgreSQL doesn't permit multiple transactions concurrently ?
Ezequias
2007/2/12, Scott Marlowe <[EMAIL PROTECTED]>:
On Mon, 2007-02-12 at 11:43, Ezequias Rodrigues da Roc
On Mon, 2007-02-12 at 11:43, Ezequias Rodrigues da Rocha wrote:
> Hi list,
>
> I am curious becouse I am seen my postgresql locking the transactions
> when i load a huge (in some case not to huge) numbers of records
> 70,000 records.
>
> Could someone help me with it ?
Are sure that what you're
11 matches
Mail list logo
