From: Marcus Whitney <marcus@coldfeetcreative.com>
To: pgsql-sql@postgresql.org
Subject: Re: pl/pgsql and transaction locks
Date: Mon, 7 Jun 2004 13:24:53 -0500
Message-ID: <200406071324.53601.marcus@coldfeetcreative.com> (raw)
Hello,
I have an instance where I have a series of pl/pgsql calls, that report stat
results to a common table. When other queries try to hit the stat table
(with DML commands; SELECT, INSERT, UPDATE, DELETE etc.) they are forced to
wait in a queue until the pl/pgsql has finished executing.
will:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
before these DML queries eliminate the locking?
--
marcus whitney
chief architect : cold feet creative
www.coldfeetcreative.com
800.595.4401
cold feet presents emma
email marketing for discriminating
organizations everywhere
visit www.myemma.com
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: marcus@coldfeetcreative.com
Subject: Re: pl/pgsql and transaction locks
In-Reply-To: <200406071324.53601.marcus@coldfeetcreative.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