Thread: Ways to check the status of a long-running transaction
I recall this being discussed before, but I couldn't manage to find it in the archives. Is there any way to see how many rows a running transaction has written? vacuum analyze verbose only reports visible rows. -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
"Jim C. Nasby" <decibel@decibel.org> writes: > I recall this being discussed before, but I couldn't manage to find it > in the archives. > > Is there any way to see how many rows a running transaction has written? > vacuum analyze verbose only reports visible rows. Not AFAIK. In the past I've done ls -l and then divided by the average row size. But that required some guesswork and depended on the fact that I was building the table from scratch. I think there's a tool to dump the raw table data which might be handy if you know the table didn't have a lot of dead tuples in it. It would be *really* handy to have a working dirty read isolation level that allowed other sessions to read uncommitted data. -- greg