Re: Infinite waitOnLock

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Leonard Meyer <lmeyer(at)excilys(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Infinite waitOnLock
Date: 2014-12-09 20:19:09
Message-ID: 704661042.4580149.1418156349661.JavaMail.yahoo@jws10046.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Leonard Meyer <lmeyer(at)excilys(dot)com> wrote:
> 2014-12-04 16:30 GMT+01:00 Kevin Grittner <kgrittn(at)ymail(dot)com>:
>> Leonard Meyer <lmeyer(at)excilys(dot)com> wrote:

>>> We're doing an ETL Akka application using PostgreSQL 9.3.5
>>> using driver 9.3-1102-jdbc41. We're currently testing our
>>> application resilience by shutting down the database in the
>>> middle of our processing.
>>
>> *Exactly* how are you "shutting down the database"?

> We call stop on the postgresql service so "sudo service
> postgresql stop".

Hmm. That shouldn't prevent the client side from seeing the
connection as closed (as would happen if the network was unplugged
or the server abruptly turned off) -- so the TCP keepalive settings
should not come into play. Given that, it does sound like a likely
bug in the JDBC driver. The best place to report that is the
pgsql-jdbc list; I don't think that the people who do most of the
work on the JDBC driver tend to read this pgsql-bug list. Please
post there, and include that stack trace again.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2014-12-09 20:24:06 Re: BUG #11986: psql uses pager inside Emacs shell buffer (not a terminal)
Previous Message Alvaro Herrera 2014-12-09 18:24:54 Re: regression, deadlock in high frequency single-row UPDATE