Re: Query on pg_stat_activity table got stuck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: neeraj kumar <neeru(dot)cse(at)gmail(dot)com>
Cc: Jeremy Schneider <schnjere(at)amazon(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: Query on pg_stat_activity table got stuck
Date: 2019-05-10 16:13:58
Message-ID: 28335.1557504838@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

neeraj kumar <neeru(dot)cse(at)gmail(dot)com> writes:
> Also curious why query on pg_stat_activity is considering terminated
> process ?

The short answer to that is that this bug leaves shared memory in
a corrupt state. It's not really useful to worry about whether
readers should react differently to that --- you could spend endless
amounts of time hypothesizing different kinds of corruption and
endless amounts of code/cycles trying to work around it. But the
right answer is to fix it on the writing side.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message neeraj kumar 2019-05-10 20:32:54 Re: Query on pg_stat_activity table got stuck
Previous Message neeraj kumar 2019-05-10 15:40:44 Re: Query on pg_stat_activity table got stuck

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-05-10 16:14:16 Re: perl path issue
Previous Message Adrian Klaver 2019-05-10 16:02:53 Re: Question about Expected rows value in EXPLAIN output for Nested Loop node