[EMAIL PROTECTED] (Ron Johnson) writes:
> On 10/16/07 08:21, hubert depesz lubaczewski wrote:
>> hi,
>> would it be possible for someone to add "last query" for
>> pg_stat_activity view?
>>
>> there is a lot of cases that we have "idle in transaction" sitting for
>> long time, and since we dont lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/16/07 08:21, hubert depesz lubaczewski wrote:
> hi,
> would it be possible for someone to add "last query" for
> pg_stat_activity view?
>
> there is a lot of cases that we have "idle in transaction" sitting for
> long time, and since we dont log
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 yo
hubert depesz lubaczewski <[EMAIL PROTECTED]> writes:
> would it be possible for someone to add "last query" for
> pg_stat_activity view?
> there is a lot of cases that we have "idle in transaction" sitting for
> long time, and since we dont log all queries it is next to impossible to
> tell where
hi,
would it be possible for someone to add "last query" for
pg_stat_activity view?
there is a lot of cases that we have "idle in transaction" sitting for
long time, and since we dont log all queries it is next to impossible to
tell where in app code the problem lies.
it would be very useful to g
