[14:49] <teward> someone want to check on some timeouts for me?  OOPS-6de0d4afdcb5bfbdb7e2d2eb76267fe1
[14:50] <teward> because it's preventing me filing a bug about the Canonical SSO system being borken
[14:53] <teward> also OOPS-4706127e6755fd31c93a3763b2dd96f9 and OOPS-2480e645e7a849eb01e32f0824d90073
[14:54] <cjwatson> That's a known class of transient timeouts; wait ten minutes or so and try again
[14:55] <teward> mmkay.
[14:56] <teward> cjwatson: and if it still breaks after that?
[14:56] <teward> (the first oops ID is missing, but it was over 15 minutes ago
[14:56] <teward> I lost it because i tried again :| )
[14:56] <cjwatson> can't help further I'm afraid - this has always gone away in a relatively short timescale before
[14:56] <teward> mmkay.
[14:57] <cjwatson> we don't know the exact cause but it appears to be some kind of occasional internal maintenance task inside postgresql that blocks some of our triggers