Blocking connection and timeout problem

From: KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at>
To:
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Blocking connection and timeout problem
Date: 2005-08-03 11:23:05
Message-ID: ED4E30DD9C43D5118DFB00508BBBA76EB1681E@neptun.sonorys.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

I managed to reproduce a locking problem, which is about blocking
transactions and dead connections. How can this be avoided?

What I did was:
1. Start a transaction on Client A
2. Execute a fcn doing an UPDATE on a certain record on client A
3. Execute a fcn doing an UPDATE on the same record on client B
/ as expected SQL on client B stalls untl client A's transaction ends/
4. disconnect client A's network cable
5. kill the psql on client A
/ C.A's transaction still runs since two hours, C.B's SQL lasts for equal
that time/
6. wait on client B's statement to finish...
7. kill -TERM client A's postmaster
/ client B's statement succeeds

Why is that? Why isn't client A's transaction detected as dead ? Yes,
because the socked wasn't closed due to a network error. But this can happen
all the time. What can I do?

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Vahe Ghorghorian 2005-08-03 11:30:06 Hello
Previous Message Steulet Grégory 2005-08-03 08:46:34 hot backup