Help: I have a postgres deadlock happening fairly reproducibly, but only when I run tests on travis' sudo: false infra.
-
-
Replying to @Carols10cents
Tried pulling down a travis image locally and running in docker, can't reproduce. Tried `sudo: required`, can't reproduce.
1 reply 0 retweets 0 likes -
Replying to @Carols10cents
This is a problem bc afaict, the only way to get more info about the deadlock is change logging cfg, which reqs pg restart, which reqs sudo
1 reply 0 retweets 0 likes -
Replying to @Carols10cents
Any postgres experts have ideas for how to get more info on a deadlock without needing a postgres restart to pick up a config change...?
2 replies 2 retweets 1 like -
-
Replying to @Carols10cents
hi, you can change the log info (log_min_duration_statement from -1 to 0) and send a HUP of the server (kill -HUP)
1 reply 0 retweets 1 like
Replying to @itManuel
thank you! i will give that a try :)
1:01 PM - 23 Dec 2016
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.