Matt Mello <alien(at)spaceship(dot)com> writes:
> I just got a "deadlock detected" SQL error from the backend. I've never
> received one of these before, but I just released new pooling code, so
> I'm concerned.
> Can someone point me to documentation on what this is and how to prevent
> it? [My search on the newsgroups yielded far too much for me to read.]
It means user A is waiting for a lock held by user B, while user B
is waiting for a lock held by user A. For better info you'll need
to offer more details about what your applications are doing ...
regards, tom lane