On Mittwoch, 9. Juli 2008 Josh Berkus wrote: > On PostgreSQL, the way you do this is by adding log_statement and > log_duration options, which will add queries and their execution > times to the activity log.
I just found in the postgres config:
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations, in milliseconds.
Looks like that should be enough for a query log. Would I still need
log_statement=all, or is =ddl enough?
I'll give that a try once, if somebody wanted it for an analyze. I am
not good enough to optimize sql queries, but willing to share that log
for stats.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: www.keyserver.net Key-ID: 1C1209B4
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
