I do something similiar, but I don't see these delays. Do you have more details about your circumstance? pgtcl version, PG version, how big the table is, what kind of processing is being done in the script, etc. Have you tried simply debugging in the script to see where the bottleneck may lay? For example, doing a simply puts with clock at various points in the script.
----- Original Message ----
From: Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca>
Sent: Tuesday, October 24, 2006 6:10:55 PM
Subject: [INTERFACES] pg_exec commit causes extremely long delays
I have a TCL app which has severe delays - measured in tens of minutes at
least - running "pg_exec $conn "commit".
The delays are so long that I used to think the app was hopelessly frozen.
By accident, I left the app alone in its frozen state and came back a good
eal later and seen that it was running again. The application loops through
an import file, reading one row at a time, and issues a bunch of inserts and
updates to various tables. There's a simple pg_exec $conn "start
transaction" at the beginning of the loop and the commit at the end.
There are a minimum of four apps running at the same time, all reading
different sections of the same table, all writing to the same db and the
same tables. The other apps seem unaffected by the one app that freezes.
Any thoughts on the cause and possible solutions would be appreciated.
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
pgsql-interfaces by date
|Next:||From: Carlo Stonebanks||Date: 2006-10-28 21:25:53|
|Subject: Re: pg_exec commit causes extremely long delays|
|Previous:||From: Sean Davis||Date: 2006-10-27 10:53:18|
|Subject: Re: How to get table definition of a PostgreSQL table|