From: Marcus Whitney <marcus@coldfeetcreative.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: pl/pgsql and Transaction Isolation
Date: Tue, 8 Jun 2004 09:19:44 -0500
Message-ID: <200406080919.45031.marcus@coldfeetcreative.com> (raw)
In-Reply-To: <25924.1086668975@sss.pgh.pa.us>
References: <200406071131.46488.marcus@coldfeetcreative.com>
<25924.1086668975@sss.pgh.pa.us>
You were right not to believe it. I had an update on a whole table that I
hadn't noticed. Thanks for debunking.
On Monday 07 June 2004 23:29, you wrote:
> Marcus Whitney <marcus@coldfeetcreative.com> writes:
> > 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.
>
> This is quite hard to believe, unless your pl/pgsql is doing something
> as unfriendly as LOCKing the table.
>
> Do you want to post a more complete description of your problem?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
marcus whitney
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-performance@postgresql.org
Cc: marcus@coldfeetcreative.com, tgl@sss.pgh.pa.us
Subject: Re: pl/pgsql and Transaction Isolation
In-Reply-To: <200406080919.45031.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