Search Postgresql Archives

Re: Ways to check the status of a long-running transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Jim C. Nasby" <decibel@xxxxxxxxxxx> 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


---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux