can't remember. At the very least I could clone that graph and make a lenny-only version.
2012-08-01 21406, 2012
ocharles
that would certainly be sufficient
2012-08-01 21450, 2012
djce
done
2012-08-01 21418, 2012
noobie joined the channel
2012-08-01 21402, 2012
ocharles
great! thanks a bunch :)
2012-08-01 21441, 2012
ijabz joined the channel
2012-08-01 21413, 2012
ijabz_ joined the channel
2012-08-01 21441, 2012
warp *facepalm*
2012-08-01 21450, 2012
warp
ocharles: had some fun with data in my /ws/2 json tests being slightly different from what I expected.
2012-08-01 21442, 2012
warp
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 >_<
2012-08-01 21401, 2012
ocharles
warp: that's odd, because a test context uses a null cache
2012-08-01 21407, 2012
warp
(yes, it took me way too long before I realized that was going on)
2012-08-01 21429, 2012
warp
ocharles: hmm, odd. I'll see if I can consistently reproduce it.
2012-08-01 21448, 2012
warp
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
2012-08-01 21423, 2012
ianmcorvidae
hm, looks like no
2012-08-01 21456, 2012
ocharles
no, i haven't worked out how
2012-08-01 21415, 2012
ocharles
totoro looks fine
2012-08-01 21434, 2012
ocharles
hmm, not entirely fine...
2012-08-01 21438, 2012
ocharles
LOG: process 8008 acquired ShareLock on transaction 475590401 after 383689.608 ms
2012-08-01 21451, 2012
ruaok joined the channel
2012-08-01 21422, 2012
ocharles
ok, I think I know the problem
2012-08-01 21410, 2012
ocharles
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
2012-08-01 21423, 2012
ianmcorvidae
weird
2012-08-01 21430, 2012
ocharles
but because the exception is rethrow in the web site, the transaction doesn't get rolled back
2012-08-01 21439, 2012
ocharles
hence the transaction is never closed, and the locks are never released
so we can be sure a frontend should have killed it
2012-08-01 21446, 2012
ocharles
or 31 if you want to go as small as possible
2012-08-01 21456, 2012
ruaok
deployed with 40
2012-08-01 21457, 2012
ocharles
i'm not sure this code is right actually
2012-08-01 21426, 2012
ocharles
ruaok: uhh, scalar(localtime) > $idle doesn't make any sense :)
2012-08-01 21434, 2012
ocharles
that just checks 'is now greater than 20 seconds'
2012-08-01 21417, 2012
ruaok
heh
2012-08-01 21442, 2012
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}
2012-08-01 21451, 2012
ruaok
agreed.
2012-08-01 21405, 2012
ocharles
interval/date/time manipulation is hard, easier to just keep that in the database side of things
2012-08-01 21404, 2012
ocharles
ruaok: i'll leave this with you, I'd like to get heading home now
