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 03:25:01 |
Message-ID: | 32704.1557458701@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:
> We got more information about this issue. There is one backend process
> still present into beentry which has changecount as odd value. However this
> process is long gone/terminated. It means when this process was
> killed/terminated its entry was not cleaned from beentry list. There seems
> to be some shutdown hook which cleans beentry if process is
> killed/terminated that somehow was not kicked off ?
No, that's the point: there isn't any such cleanup code. The design
idea here was that we'd only have short straight-line code segments
with no possible way to throw an error while changecount is odd.
Then somebody abused the heck out of that ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | neeraj kumar | 2019-05-10 03:34:37 | Re: Query on pg_stat_activity table got stuck |
Previous Message | neeraj kumar | 2019-05-09 23:35:37 | Re: Query on pg_stat_activity table got stuck |
From | Date | Subject | |
---|---|---|---|
Next Message | neeraj kumar | 2019-05-10 03:34:37 | Re: Query on pg_stat_activity table got stuck |
Previous Message | Bruce Momjian | 2019-05-10 01:20:36 | Re: Oracle Migration Approach (Open source vs Vendor Specific) |