Could you do this by setting debug-level higher and do log-analysis?
BTW, it might be nice to give the backends a diagnostic port for "remote
debugging" in similar wise as the Java Virtual Machine provides so that some
degree of live-time workflow examination can happen. What do you think?
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Steve Atkins
Sent: Monday, June 28, 2004 1:34 PM
Subject: [GENERAL] Seeing uncommitted transactions
Is there any way to look at the database as though you were inside another
I've had two cases recently where this would have been somewhat useful. In
one, a select into query ran for several hours and it would have been nice
to see that it was running correctly. In the other an application threw a
spurious BEGIN into the stream of operations, meaning that changes made
weren't visible to the rest of the world until it started another
transaction (which was ignored) and then committed it.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
In response to
pgsql-general by date
|Next:||From: Justin Clift||Date: 2004-06-29 03:59:11|
|Subject: How to determine field names in a trigger?|
|Previous:||From: Thomas Hallgren||Date: 2004-06-28 23:08:45|
|Subject: Re: Plperlu and sending emails, is it safe?|