From: Andreas Kretschmer <akretschmer@spamfence.net>
To: pgsql-sql@postgresql.org
Subject: Re: [ADMIN] Deadlock on transaction
Date: Mon, 12 Feb 2007 19:45:48 +0100
Message-ID: <20070212184548.GA2090@KanotixBox> (raw)
In-Reply-To: <55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com>
<1171302488.3565.15.camel@state.g2switchworks.com>
<55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com> 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 case. PG works fine with many users on many
connections and many transactions, at the same time.
>
> Ezequias
>
> 2007/2/12, Scott Marlowe <_s_m_a_r_l_o_w_e_@_g_2_s_w_i_t_c_h_w_o_r_k_s_._c_o_m>:
Please, no silly fullquote betlow the answer and no html.
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknow)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
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: akretschmer@spamfence.net
Subject: Re: [ADMIN] Deadlock on transaction
In-Reply-To: <20070212184548.GA2090@KanotixBox>
* 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