Craig Vosburgh <craig.vosburgh@xxxxxxxxxxx> writes: > We've dumped the locks and it shows that all locks have been granted so > it appears that it is not a lock that is standing in our way. We've > also gone in via psql while the update is hung and were able to perform > an update on the offending table without issue. Finally, we have also > enabled the statement_timeout and set it to five minutes and it does > timeout the hung update and return to normal processing by rolling back > the offending transaction but that's not a viable solution for us. > Anyone have any words of wisdom on how to track this down? For starters, attach to the hung backend with gdb and get a stack trace ... regards, tom lane
