Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 607B1B5DBD6 for ; Wed, 17 Aug 2011 11:34:37 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 22479-01 for ; Wed, 17 Aug 2011 14:34:31 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.49]) by mail.postgresql.org (Postfix) with ESMTP id 97F64B5D80A for ; Wed, 17 Aug 2011 11:34:30 -0300 (ADT) Received: (qmail 14620 invoked from network); 17 Aug 2011 14:34:30 -0000 Received: from 25-76-42-72.skybeam.com (HELO [192.168.2.16]) (sribe@elevated-dev.com@[72.42.76.25]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 17 Aug 2011 14:34:30 -0000 Subject: Re: Using Postgresql as application server Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Scott Ribe In-Reply-To: <4E4B6828.1050506@compulab.co.il> Date: Wed, 17 Aug 2011 08:34:29 -0600 Cc: pgsql-general@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <46EC79AF-3685-484E-AABE-E25969C23D56@elevated-dev.com> References: <4E498536.9080109@darrenduncan.net> <008301cc5b95$e287b120$a7971360$@yahoo.com> <4E49A208.5070604@darrenduncan.net> <4E49EC4D.1090707@darrenduncan.net> <4E4B6828.1050506@compulab.co.il> To: Sim Zacks X-Mailer: Apple Mail (2.1084) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201108/558 X-Sequence-Number: 178840 On Aug 17, 2011, at 1:05 AM, Sim Zacks wrote: > 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. 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. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice