can't remember. At the very least I could clone that graph and make a lenny-only version.
ocharles
that would certainly be sufficient
djce
done
noobie joined the channel
ocharles
great! thanks a bunch :)
ijabz joined the channel
ijabz_ joined the channel
warp *facepalm*
warp
ocharles: had some fun with data in my /ws/2 json tests being slightly different from what I expected.
ocharles: the tests still get stuff from the running memcached, so if "production" data differs from t/sql/webservice.sql and has been recently viewed it will affect the tests >_<
ocharles
warp: that's odd, because a test context uses a null cache
warp
(yes, it took me way too long before I realized that was going on)
ocharles: hmm, odd. I'll see if I can consistently reproduce it.
ocharles: ok, it's not happening now. I guess I did change something else right before/after I restarted memcached. grmbl.
ianmcorvidae wonders if they added locks to the pg stats
ianmcorvidae
hm, looks like no
ocharles
no, i haven't worked out how
totoro looks fine
hmm, not entirely fine...
LOG: process 8008 acquired ShareLock on transaction 475590401 after 383689.608 ms
ruaok joined the channel
ok, I think I know the problem
I think a process encountered a deadlock after it had managed to hold some locks. the deadlock subsequently aborted the transaction, but did not release the locks
ianmcorvidae
weird
ocharles
but because the exception is rethrow in the web site, the transaction doesn't get rolled back
hence the transaction is never closed, and the locks are never released
so we can be sure a frontend should have killed it
or 31 if you want to go as small as possible
ruaok
deployed with 40
ocharles
i'm not sure this code is right actually
ruaok: uhh, scalar(localtime) > $idle doesn't make any sense :)
that just checks 'is now greater than 20 seconds'
ruaok
heh
ocharles
i think it'd be much easier to amend that SELECT to have "current_query = '<IDLE> in transaction' AS idle_transaction" and then check if $stuck->{idle_transaction}
ruaok
agreed.
ocharles
interval/date/time manipulation is hard, easier to just keep that in the database side of things
ruaok: i'll leave this with you, I'd like to get heading home now