pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: marcus@coldfeetcreative.com
Cc: pgsql-performance@postgresql.org
Subject: Re: pl/pgsql and Transaction Isolation
Date: Tue, 08 Jun 2004 00:29:35 -0400
Message-ID: <25924.1086668975@sss.pgh.pa.us> (raw)
In-Reply-To: <200406071131.46488.marcus@coldfeetcreative.com>
References: <200406071131.46488.marcus@coldfeetcreative.com>

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



view thread (3+ messages)  latest in thread

Message-ID: <25924.1086668975@sss.pgh.pa.us>
Permalink:  ../25924.1086668975@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25924.1086668975@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, marcus@coldfeetcreative.com
  Subject: Re: pl/pgsql and Transaction Isolation
  In-Reply-To: <25924.1086668975@sss.pgh.pa.us>

* 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