pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pl/pgsql and Transaction Isolation
3+ messages / 2 participants
[nested] [flat]

* pl/pgsql and Transaction Isolation
@ 2004-06-07 16:31 Marcus Whitney <marcus@coldfeetcreative.com>
  2004-06-08 04:29 ` Re: pl/pgsql and Transaction Isolation Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Marcus Whitney @ 2004-06-07 16:31 UTC (permalink / raw)
  To: pgsql-performance

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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pl/pgsql and Transaction Isolation
  2004-06-07 16:31 pl/pgsql and Transaction Isolation Marcus Whitney <marcus@coldfeetcreative.com>
@ 2004-06-08 04:29 ` Tom Lane <tgl@sss.pgh.pa.us>
  2004-06-08 14:19   ` Re: pl/pgsql and Transaction Isolation Marcus Whitney <marcus@coldfeetcreative.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2004-06-08 04:29 UTC (permalink / raw)
  To: marcus@coldfeetcreative.com; +Cc: pgsql-performance

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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pl/pgsql and Transaction Isolation
  2004-06-07 16:31 pl/pgsql and Transaction Isolation Marcus Whitney <marcus@coldfeetcreative.com>
  2004-06-08 04:29 ` Re: pl/pgsql and Transaction Isolation Tom Lane <tgl@sss.pgh.pa.us>
@ 2004-06-08 14:19   ` Marcus Whitney <marcus@coldfeetcreative.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Marcus Whitney @ 2004-06-08 14:19 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-performance

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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2004-06-08 14:19 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-06-07 16:31 pl/pgsql and Transaction Isolation Marcus Whitney <marcus@coldfeetcreative.com>
2004-06-08 04:29 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-06-08 14:19   ` Marcus Whitney <marcus@coldfeetcreative.com>

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