Idle in transcation problem?

Started by Charles.Houover 17 years ago2 messagesgeneral
Jump to latest
#1Charles.Hou
ivan.hou@msa.hinet.net

i use the "ps -ef | grep postgres" to see all the connections. the
connection's status is "Idle in transcation".

and i use the " du -h /mydb" to check the disk size. The disk size of
mydb has increased from 400MB to 600MB.
Why? because of the "idle in transcation" ?

my pg version:8.1.3
OS: Linux Enterprise 4

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Charles.Hou (#1)
Re: Idle in transcation problem?

"Charles.Hou" <ivan.hou@msa.hinet.net> writes:

i use the "ps -ef | grep postgres" to see all the connections. the
connection's status is "Idle in transcation".

and i use the " du -h /mydb" to check the disk size. The disk size of
mydb has increased from 400MB to 600MB.
Why? because of the "idle in transcation" ?

Maybe. Old open transactions would prevent VACUUM from removing deleted
row versions (because they might still be visible to those
transactions). So if this condition persisted for a long time it could
be responsible for table bloat. It's a good idea to make sure your
client code doesn't leave transactions sitting open for long periods.

my pg version:8.1.3

You really ought to get onto a more recent sub-release ... that one is
2.5 years old and has many known bugs.
http://www.postgresql.org/docs/8.1/static/release.html

regards, tom lane