From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: improvement proposition |
Date: | 2007-10-16 17:09:34 |
Message-ID: | 20071016170933.GA9398@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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)
From | Date | Subject | |
---|---|---|---|
Next Message | jehan.procaccia | 2007-10-16 17:12:36 | move databases files location |
Previous Message | Richard Huxton | 2007-10-16 16:59:22 | Re: Preserving view source code |