procpid in pg_stat_activity but no correspoding backend

[Rajesh Kumar Mallah]

Hi ,

I noticed that an entry in pg_stat_activity was existing for a
long duration > 2 mins while its backend ( process corresponding
to that procpid) was not running.

how can it be possible ?

version: 7.3.4
regds
mallah.
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Jan Wieck]

Rajesh Kumar Mallah wrote:

Hi ,

I noticed that an entry in pg_stat_activity was existing for a
long duration > 2 mins while its backend ( process corresponding
to that procpid) was not running.

how can it be possible ?

version: 7.3.4

There was a bug that caused a crashing backend to hang around in the
stats until the slot is reused, because the message telling that the
backend terminates is never sent to the collector daemon. I'm not sure
if that got fixed for 7.4.
Jan

--
#================================================= =====================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================= = Ja******@Yahoo.com #
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

[Rajesh Kumar Mallah]

Jan Wieck wrote:

Rajesh Kumar Mallah wrote:

Hi ,

I noticed that an entry in pg_stat_activity was existing for a
long duration > 2 mins while its backend ( process corresponding
to that procpid) was not running.

how can it be possible ?

version: 7.3.4

There was a bug that caused a crashing backend to hang around in the
stats until the slot is reused, because the message telling that the
backend terminates is never sent to the collector daemon. I'm not sure
if that got fixed for 7.4.

Thanks for explaining.

Regds
Mallah.

Jan

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly