A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Tom Lane) wrote:
> Chris Browne <[EMAIL PROTECTED]> 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
Chris Browne <[EMAIL PROTECTED]> 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 t
[EMAIL PROTECTED] (Tom Lane) writes:
> Chris Browne <[EMAIL PROTECTED]> writes:
>> We're getting a bit of an anomaly relating to pg_stat_activity...
>> ...
>> That PID has been dead for several days, but this connection is marked
>> as being open, still, after lo many days.
>
> This probably just m
Chris Browne <[EMAIL PROTECTED]> writes:
> We're getting a bit of an anomaly relating to pg_stat_activity...
> ...
> That PID has been dead for several days, but this connection is marked
> as being open, still, after lo many days.
This probably just means that the "backend termination" stats mess
