On Tue, Oct 16, 2007 at 11:16:46AM -0400, Tom Lane wrote:
> Turn on log_statement. I don't believe the feature you are asking for
> will be nearly as useful as you think. More than likely, what it
> will show you is something like "commit; begin" and you'll be little
> wiser than before. What you'll need to identify the problem will be a
> trace of everything the app did; which is what the log is for, not
> pg_stat_activity.
logging all statements is possible (this is what i do now), but it is
far from optimal - it generates 500 megabytes of logs every 10 minutes.
on the other hand - doing log analysis i did found the problem (and it
was not commit; begin thing) - i was simply hoping for simpler, and less
intrusive way of getting the data.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA. here's my CV!" :)
http://www.depesz.com/ - blog dla ciebie (i moje CV)
