| 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:59:14 |
| Message-ID: | CA+hUKG+okrN2e_GrWrYVGd8+uVznAUPNsjbgEtfY0rAdrwR-Vg@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:39 PM James Pang (chaolpan)
<chaolpan(at)cisco(dot)com> wrote:
> (gdb) p RecordCacheArray
> $1 = (TupleDesc *) 0x7f5fac365d90
> (gdb) p RecordIdentifierArray
> $2 = (uint64 *) 0x0
Hah, yeah that's it, and you've been extremely unlucky to hit it.
ensure_record_cache_typmod_slot_exists() should be more careful about
cleaning up on allocation failure, to avoid this state.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-09-07 11:05:29 | Re: BUG #18092: Unexpected Result by enable_seqscan |
| Previous Message | James Pang (chaolpan) | 2023-09-07 10:39:09 | RE: FW: query pg_stat_ssl hang 100%cpu |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-09-07 23:45:51 | Re: FW: query pg_stat_ssl hang 100%cpu |
| Previous Message | James Pang (chaolpan) | 2023-09-07 10:39:09 | RE: FW: query pg_stat_ssl hang 100%cpu |