| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | neeraj kumar <neeru(dot)cse(at)gmail(dot)com> |
| Cc: | 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-08 18:12:56 |
| Message-ID: | 21502.1557339176@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
neeraj kumar <neeru(dot)cse(at)gmail(dot)com> writes:
> Took some time to get stack trace as we didn't had root permission.
> Attaching stack trace of two process (out of many) stuck for same query
> below[1][2]
Hmm, the line numbers in your stack traces don't agree with either v10
or HEAD branches for me. But assuming that you've correctly identified
where it's stuck:
> Seems like call is unable to come out of this loop :
> https://github.com/postgres/postgres/blob/master/src/backend/postmaster/pgstat.c#L3361-L3400
the only really obvious theory is that some process left its
st_changecount odd, which would more or less have to imply that
something threw an error between pgstat_increment_changecount_before
and pgstat_increment_changecount_after. There's only one place
where that seems very plausible, namely pgstat_bestart, which is
doing a rather scary amount of stuff in between. Are you using
either SSL or GSS?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | neeraj kumar | 2019-05-08 21:21:06 | Re: Query on pg_stat_activity table got stuck |
| Previous Message | neeraj kumar | 2019-05-08 17:42:12 | Re: Query on pg_stat_activity table got stuck |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-05-08 19:07:50 | Re: postgresql 9.4 restart |
| Previous Message | Julie Nishimura | 2019-05-08 18:00:19 | postgresql 9.4 restart |