From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: Deadlock on transaction
Date: Mon, 12 Feb 2007 11:48:08 -0600
Message-ID: <1171302488.3565.15.camel@state.g2switchworks.com> (raw)
In-Reply-To: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com>
References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com>
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 speaking of is a deadlock? Or is it just a
stalled transaction while one one transaction waits for another to
complete?
A true deadlock means that two transactions are stalled waiting for the
other to complete, and neither ever can complete, and they are
DEADlocked.
If you've just got a problem where an update is stalling all the other
transactions, then give us a test case / example code of what's
happening.
If you've got a real deadlock that postgresql isn't catching, that's a
much more serious problem.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: smarlowe@g2switchworks.com, ezequias.rocha@gmail.com, pgsql-admin@postgresql.org
Subject: Re: Deadlock on transaction
In-Reply-To: <1171302488.3565.15.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox