<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="latin-charset" bgcolor="#ffffff"
text="#000000">
On 08/17/2011 05:34 PM, Scott Ribe wrote:
<blockquote
cite="mid:46EC79AF-3685-484E-AABE-E25969C23D56(at)elevated-dev(dot)com"
type="cite">
<pre wrap="">On Aug 17, 2011, at 1:05 AM, Sim Zacks wrote:
</pre>
<blockquote type="cite">
<pre wrap="">One problem we have with LISTEN/NOTIFY (and I haven't found the cause for this yet) is every once in a while my daemon stops listening. It may be after a month of use or longer, and may be caused by the database being restarted or something similar. When the daemon stops listening, it doesn't give any errors or indication that it isn't working anymore.
</pre>
</blockquote>
<pre wrap="">
So your daemon has a bug. When the database is restarted, connections will be closed, and the daemon should certainly notice that. Of course the cause may be something else, but either way I doubt it's a problem with NOTIFY/LISTEN.
</pre>
</blockquote>
<p>The point was not whether I have a bug in an external
application, the point is that I need an external application
which creates more overhead and another point of failure in the
application stack. <br>
</p>
</body>
</html>