Skip site navigation (1) Skip section navigation (2)

Re: Stats Collector Oddity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats Collector Oddity
Date: 2006-12-21 16:30:27
Message-ID: 20277.1166718627@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Chris Browne <cbbrowne(at)acm(dot)org> writes:
> There isn't any way, short of restarting the postmaster, to get rid of
> that PID, is there?

The entry will get overwritten when that BackendId slot gets re-used,
so just starting enough concurrent backends should do it.  (Since
incoming backends always take the lowest free slot, the fact that the
dead entry has persisted awhile means that it must have a number higher
than your normal number of concurrent sessions ... which is evidence
in favor of the idea that it happened during a load spike ...)

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Lukas Kahwe SmithDate: 2006-12-21 16:33:14
Subject: Re: Release 8.2.0 done, 8.3 development starts
Previous:From: Andrew DunstanDate: 2006-12-21 16:27:44
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group