From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Boes <jboes@nexcerpt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Contents of pg_listener linger?
Date: Fri, 06 Feb 2004 10:44:48 -0500
Message-ID: <196.1076082288@sss.pgh.pa.us> (raw)
In-Reply-To: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com>
References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com>
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?
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
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: tgl@sss.pgh.pa.us, jboes@nexcerpt.com
Subject: Re: Contents of pg_listener linger?
In-Reply-To: <196.1076082288@sss.pgh.pa.us>
References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com> <196.1076082288@sss.pgh.pa.us>
* 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