On 08/17/2011 05:34 PM, Scott Ribe wrote: <blockquote cite="mid:46EC79AF-3685-484E-AABE-E25969C23D56@elevated-dev.com"
type="cite"><prewrap="">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
thisyet) is every once in a while my daemon stops listening. It may be after a month of use or longer, and may be
causedby the database being restarted or something similar. When the daemon stops listening, it doesn't give any errors
orindication 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
noticethat. 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
externalapplication which creates more overhead and another point of failure in the application stack. <br />
