Ben,
It turns out that 7.2 has neither of those options you will have to set
the debug_level to something higher than 0 and less than 4 to get
information out. I'm afraid I'm not sure which value will give you what
you are looking for.
The link below explains what is available, and it isn't muc
I know 7.2 is old I'm trying to fix this in the mean time moving
everything to the latest Linux software when RedHat releases the
enterprise with 2.6. Postgres complains about log_duration and
log_statement are they a different name under 7.2? Is there
documentation on the type of logging the p
Ben,
Hmmm... ok 7.2.4 is quite old now and log_duration doesn't exist in the
logging. You will see an immediate performance benefit just by moving to
7.4.x, but I'll bet that's not a reasonable path for you.
in postgresql.conf you can change the logging to:
log_pid=true
log_duration=true
log_sta
I am running postgresql 7.2.4-5.73, Dual P4, 1GB Ram. The big problem
is that I redirect all internal port 80 traffic to my web server so I
see all traffic whether it is a virus or not and intended for my server
or not. I originally had a problem with running out of memory but I
found a bug in
Ben
Well, we need more information
pg version, hardware, memory, etc
you may want to turn on log_duration to see exactly which statement is
causeing the problem. I'm assuming since it is taking a lot of CPU it
will take some time to complete( this may not be true)
On your last point, that is whe
