Re: Question about PostgreSQL logging configuration

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> So at end I getting logs which are incompatible with pgFouine (and
> with my custom log analyzer as well).

Ah, well, that's hardly Postgres' fault is it? :) You might want
to look into other log software - there are at least two others
I know of off the top of my head (PGSI, pgbadger) that might
be better at parsing. Or submit a bug to the pgfouine folks.

> Is there anyone who consciously used log_duration = on without
> log_statements = all ?
> And if yes - what for?
>
> I might be very wrong, but log_duration seems close to useless knob in reality.

- From the docs on log_duration:

"The difference between setting this option and setting
log_min_duration_statement to zero is that exceeding log_min_duration_statement
forces the text of the query to be logged, but this option doesn't. Thus, if
log_duration is on and log_min_duration_statement has a positive value, all
durations are logged but the query text is included only for statements exceeding
the threshold. This behavior can be useful for gathering statistics in
high-load installations."

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201211292327
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlC4Na4ACgkQvJuQZxSWSshi8QCfcUzZMvs9ZNDK6faLrY+3Tj2R
qSAAn0GJNnKhIvpX25Il5z+PLbLk7VYo
=A3W/
-----END PGP SIGNATURE-----