| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: FW: query pg_stat_ssl hang 100%cpu |
| Date: | 2023-09-07 10:36:07 |
| Message-ID: | CA+hUKG+yZFvv+C1oxBFWiHNsay+uVN8LXTwFsntE5NTh4dwahQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
On Thu, Sep 7, 2023 at 10:31 PM James Pang (chaolpan)
<chaolpan(at)cisco(dot)com> wrote:
> Yes, checked the server history logs, we found when the backend starting hang there, operating system has out of memory that may lead to the allocation of RecordIdentierArray failed.
Can you please print out RecordCacheArray and RecordIdentifierArray?
For that theory, the first one must be non-NULL and the second one
NULL. That would lead to the infinite loop, I think.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pang (chaolpan) | 2023-09-07 10:39:09 | RE: FW: query pg_stat_ssl hang 100%cpu |
| Previous Message | James Pang (chaolpan) | 2023-09-07 10:31:25 | RE: FW: query pg_stat_ssl hang 100%cpu |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pang (chaolpan) | 2023-09-07 10:39:09 | RE: FW: query pg_stat_ssl hang 100%cpu |
| Previous Message | James Pang (chaolpan) | 2023-09-07 10:31:25 | RE: FW: query pg_stat_ssl hang 100%cpu |