Re: pl/pgsql and Transaction Isolation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: marcus(at)coldfeetcreative(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: pl/pgsql and Transaction Isolation
Date: 2004-06-08 04:29:35
Message-ID: 25924.1086668975@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Marcus Whitney <marcus(at)coldfeetcreative(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2004-06-08 05:18:22 Re: Join slow on "large" tables
Previous Message Duane Lee - EGOVX 2004-06-07 23:31:44 Re: is it possible to for the planner to optimize this