Re: Seeing uncommitted transactions
От | Carl E. McMillin |
---|---|
Тема | Re: Seeing uncommitted transactions |
Дата | |
Msg-id | 000a01c45d6c$b26d3890$6500a8c0@DEVSONY обсуждение исходный текст |
Ответ на | Seeing uncommitted transactions (Steve Atkins <steve@blighty.com>) |
Ответы |
Re: Seeing uncommitted transactions
|
Список | pgsql-general |
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? Carl <|};-)> -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Steve Atkins Sent: Monday, June 28, 2004 1:34 PM To: pgsql-general@postgresql.org Subject: [GENERAL] Seeing uncommitted transactions Is there any way to look at the database as though you were inside another sessions transaction? 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. Cheers, Steve ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
В списке pgsql-general по дате отправления: