Skip site navigation (1) Skip section navigation (2)

Re: Deadlock detection

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Deadlock detection
Date: 2009-01-21 10:13:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Simon Riggs wrote:

> I'm thinking of some simple bookkeeping, so that before any session
> issues a blockable call it takes note that it is doing so in a shared
> array, and clears that state again once released. A single watcher
> thread can then regularly scan the state array and see if a session is
> marked as waiting on both send and receive. Side threads are already
> used for login timeout handling, so that mechanism is already in use.
> Some loss of performance would be acceptable.

I don't see how this can work. The whole point is that if we're blocked
on send, we're *not* blocked on receive by definition.


In response to

pgsql-jdbc by date

Next:From: Oliver JowettDate: 2009-01-21 10:38:05
Subject: Re: Deadlock detection
Previous:From: Oliver JowettDate: 2009-01-21 10:09:18
Subject: Re: Deadlock detection

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group