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 38C9FD1D31D for ; Fri, 6 Feb 2004 15:44:51 +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 48618-07 for ; Fri, 6 Feb 2004 11:44:49 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9613DD1B911 for ; Fri, 6 Feb 2004 11:44:44 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i16Fim07000197; Fri, 6 Feb 2004 10:44:48 -0500 (EST) To: Jeff Boes Cc: pgsql-admin@postgresql.org Subject: Re: Contents of pg_listener linger? In-reply-to: References: Comments: In-reply-to Jeff Boes message dated "Fri, 06 Feb 2004 13:43:02 +0000" Date: Fri, 06 Feb 2004 10:44:48 -0500 Message-ID: <196.1076082288@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/78 X-Sequence-Number: 12252 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? I have a vague recollection of old bugs that prevented pg_listener rows from being scavenged during backend exit, but they're all gone AFAIK. The only remaining condition that would account for this is a crash of the listening backend, but I trust that's not what you're dealing with. 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