Hi,
On 10 May 2013 17:43, Simon Tennant <
si...@buddycloud.com> wrote:
> Prosody seems to keep one query running on postgres:
>
> postgres=# SELECT datname,procpid,current_query FROM pg_stat_activity
> ;
> datname | procpid | current_query
> --------------------+---------+------------------------------------------------------------
> buddycloud-prosody | 29028 | <IDLE> in transaction
> buddycloud-prosody | 30228 | <IDLE> in transaction
> postgres | 29539 | SELECT datname,procpid,current_query FROM
> pg_stat_activity+
>
> and the query seems to run as long as Prosody is running:
>
>
https://munin.buddycloud.com/buddycloud.com/abyss.buddycloud.com/postgres_querylength_ALL.html
>
> Should I worry?
>
> Should I worry at the lua-dbi team (Hi Matt :) or the Prosody team (Hi Matt
> again)?
You should probably worry at me.
I thought maybe perhaps LuaDBI was opening the transaction immediately
after finishing the last (so that it always had a transaction open).
But if munin is actually showing the query age as it claims to be...
that doesn't seem like the correct answer.
I have some SQL testing on my todo, and a LuaDBI release (what version
are you using by the way?). I'll see if I can reproduce this.
Regards,
Matthew