RE: FW: query pg_stat_ssl hang 100%cpu

From: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(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:39:09
Message-ID: PH0PR11MB51917DE71E58A7905A68CF37D6EEA@PH0PR11MB5191.namprd11.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

#0 ensure_record_cache_typmod_slot_exists (typmod=0) at typcache.c:1714
#1 0x000000000091185b in assign_record_type_typmod (tupDesc=<optimized out>, tupDesc(at)entry=0x27bc738) at typcache.c:2001
#2 0x000000000091df03 in internal_get_result_type (funcid=<optimized out>, call_expr=<optimized out>, rsinfo=<optimized out>,
resultTypeId=<optimized out>, resultTupleDesc=0x7ffc9dff8cd0) at funcapi.c:393
#3 0x000000000091e263 in get_expr_result_type (expr=expr(at)entry=0x2792798, resultTypeId=resultTypeId(at)entry=0x7ffc9dff8ccc,
resultTupleDesc=resultTupleDesc(at)entry=0x7ffc9dff8cd0) at funcapi.c:230
#4 0x00000000006a2fa5 in ExecInitFunctionScan (node=node(at)entry=0x273afa8, estate=estate(at)entry=0x269e948, eflags=eflags(at)entry=16) at nodeFunctionscan.c:370
#5 0x000000000069084e in ExecInitNode (node=node(at)entry=0x273afa8, estate=estate(at)entry=0x269e948, eflags=eflags(at)entry=16) at execProcnode.c:255
#6 0x000000000068a96d in InitPlan (eflags=16, queryDesc=0x273b2d8) at execMain.c:936
#7 standard_ExecutorStart (queryDesc=0x273b2d8, eflags=16) at execMain.c:263
#8 0x00007f67c2821d5d in pgss_ExecutorStart (queryDesc=0x273b2d8, eflags=<optimized out>) at pg_stat_statements.c:965
#9 0x00000000007fc226 in PortalStart (portal=portal(at)entry=0x26848b8, params=params(at)entry=0x0, eflags=eflags(at)entry=0, snapshot=snapshot(at)entry=0x0)
at pquery.c:514
#10 0x00000000007fa27f in exec_bind_message (input_message=0x7ffc9dff90d0) at postgres.c:1995
#11 PostgresMain (argc=argc(at)entry=1, argv=argv(at)entry=0x7ffc9dff9370, dbname=<optimized out>, username=<optimized out>) at postgres.c:4552
#12 0x000000000077a4ea in BackendRun (port=<optimized out>, port=<optimized out>) at postmaster.c:4537
#13 BackendStartup (port=<optimized out>) at postmaster.c:4259
#14 ServerLoop () at postmaster.c:1745
#15 0x000000000077b363 in PostmasterMain (argc=argc(at)entry=5, argv=argv(at)entry=0x256abc0) at postmaster.c:1417
#16 0x00000000004fec63 in main (argc=5, argv=0x256abc0) at main.c:209
(gdb) p RecordCacheArray
$1 = (TupleDesc *) 0x7f5fac365d90
(gdb) p RecordIdentifierArray
$2 = (uint64 *) 0x0

-----Original Message-----
From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Sent: Thursday, September 7, 2023 6:36 PM
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

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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2023-09-07 10:59:14 Re: FW: query pg_stat_ssl hang 100%cpu
Previous Message Thomas Munro 2023-09-07 10:36:07 Re: FW: query pg_stat_ssl hang 100%cpu

Browse pgsql-performance by date

  From Date Subject
Next Message Thomas Munro 2023-09-07 10:59:14 Re: FW: query pg_stat_ssl hang 100%cpu
Previous Message Thomas Munro 2023-09-07 10:36:07 Re: FW: query pg_stat_ssl hang 100%cpu