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 11:26:01 -0500
Message-ID: <711.1076084761@sss.pgh.pa.us> (raw)
In-Reply-To: <4023BE4F.4030007@nexcerpt.com>
References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com>
<196.1076082288@sss.pgh.pa.us>
<4023BE4F.4030007@nexcerpt.com>
Jeff Boes <jboes@nexcerpt.com> writes:
> Yup, that seems to be the case. When I "NOTIFY" these, they disappear.
> Any other way to clean them up?
If you're superuser you can delete rows all you want. You could
probably cons up something that deletes rows with PIDs not found in
the pg_stat_activity view.
I'm more interested in how the rows got there though. The bugs I was
thinking of were surely stomped long before 7.3.4, so if you're not
suffering crashes then you must have found a new one. Please keep an
eye on it and see if you can figure out the circumstances in which a row
gets left behind. Since you know the PIDs of the delinquent backends,
maybe you could look at the last related entries in the postmaster log
(turn on log_pid if you're not using syslog for logging).
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: <711.1076084761@sss.pgh.pa.us>
References: <de73a3cfc16466192b7b2c3a220d8445@news.teranews.com> <196.1076082288@sss.pgh.pa.us> <4023BE4F.4030007@nexcerpt.com> <711.1076084761@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