DEBUG: StartTransactionCommand

Started by Linh Luongover 24 years ago2 messagesgeneral
Jump to latest
#1Linh Luong
linh.luong@computalog.com

Hi everyone,

My linux box just recently gave me an error message "Out of memory, Check
disk space". I didn't know why and then I went to my postgres.log file and I
noticed each time I view the browser that is accessing the postgres database
it entered in 10-20 entries of
2001-10-19 11:32:37 [15652] DEBUG: StartTransactionCommand
2001-10-19 11:32:37 [15652] DEBUG: CommitTransactionCommand
in my postgres.log file.. there are also other debug statements.

My question is WHY is it doing this? Can this be avoided? If so how?

Thanks for your help

--
Linh Luong
Computalog Ltd.
Software Developer
Direct Line: (780) 416-3358
Email: linh.luong@computalog.com

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Linh Luong (#1)
Re: DEBUG: StartTransactionCommand

Linh Luong <linh.luong@computalog.com> writes:

2001-10-19 11:32:37 [15652] DEBUG: StartTransactionCommand
2001-10-19 11:32:37 [15652] DEBUG: CommitTransactionCommand
in my postgres.log file.. there are also other debug statements.

My question is WHY is it doing this? Can this be avoided? If so how?

Don't start the postmaster with debug output enabled.

Either you have a -d switch in the postmaster command line, or you've
set debugging options in postgresql.conf.

regards, tom lane