X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 60480D1D332 for ; Fri, 6 Feb 2004 16:19:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 67204-05 for ; Fri, 6 Feb 2004 12:19:28 -0400 (AST) Received: from yapok.nexcerpt.com (mail.nexcerpt.com [64.147.202.2]) by svr1.postgresql.org (Postfix) with ESMTP id 14D1CD1D2C5 for ; Fri, 6 Feb 2004 12:19:23 -0400 (AST) Received: from nexcerpt.com (DSL-NE-21.qtm.net [216.163.37.21]) (authenticated bits=0) by yapok.nexcerpt.com (8.12.8/8.12.8) with ESMTP id i16GIj6g000884 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 6 Feb 2004 11:19:05 -0500 Message-ID: <4023BE4F.4030007@nexcerpt.com> Date: Fri, 06 Feb 2004 11:18:23 -0500 From: Jeff Boes Organization: Nexcerpt, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: Contents of pg_listener linger? References: <196.1076082288@sss.pgh.pa.us> In-Reply-To: <196.1076082288@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/80 X-Sequence-Number: 12254 Tom Lane wrote: >Jeff Boes writes: > > >>What causes the contents of pg_listener to "linger" long past the lifespan of >>the associated database backend? My table has rows that I know must be days old. >> >> > >PG version? > > > 7.3.4 >In any case, if there is a row for a dead backend it should be removed >the first time someone tries to "notify" that condition name and >discovers that he can't signal the dead backend. If you've got days-old >dead rows they must be for very-infrequently-notified conditions. > > regards, tom lane > > Yup, that seems to be the case. When I "NOTIFY" these, they disappear. Any other way to clean them up? The problem is that there's one legit listener, and umpteen dead ones. I can rig up something to notify all these but I have to make sure that the legit listener is offline. -- Jeff Boes vox 269.226.9550 ext 24 Database Engineer fax 269.349.9076 Nexcerpt, Inc. http://www.nexcerpt.com ...Nexcerpt... Extend your Expertise