| From: | Marcus Whitney <marcus(at)coldfeetcreative(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: pl/pgsql and transaction locks |
| Date: | 2004-06-07 18:24:53 |
| Message-ID: | 200406071324.53601.marcus@coldfeetcreative.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
800.595.4401
cold feet presents emma
email marketing for discriminating
organizations everywhere
visit www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyle | 2004-06-07 23:57:12 | Getting FK relationships from information_schema |
| Previous Message | Stephan Szabo | 2004-06-07 14:34:53 | Re: empty string casting to typed value |