pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Boes <jboes@nexcerpt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Contents of pg_listener linger?
Date: Fri, 06 Feb 2004 11:18:23 -0500
Message-ID: <4023BE4F.4030007@nexcerpt.com> (raw)
In-Reply-To: <196.1076082288@sss.pgh.pa.us>
References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com>
	<196.1076082288@sss.pgh.pa.us>

Tom Lane wrote:

>Jeff Boes <jboes@nexcerpt.com> 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




view thread (4+ messages)  latest in thread

Message-ID: <4023BE4F.4030007@nexcerpt.com>
Permalink:  ../4023BE4F.4030007@nexcerpt.com/
Also on:    postgresql.org/message-id/4023BE4F.4030007@nexcerpt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jboes@nexcerpt.com, tgl@sss.pgh.pa.us
  Subject: Re: Contents of pg_listener linger?
  In-Reply-To: <4023BE4F.4030007@nexcerpt.com>
  References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com> <196.1076082288@sss.pgh.pa.us> <4023BE4F.4030007@nexcerpt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox