Re: FW: query pg_stat_ssl hang 100%cpu

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: FW: query pg_stat_ssl hang 100%cpu
Date: 2023-09-10 22:37:34
Message-ID: CA+hUKGJsdfVYOea0NHDdd01EWj1C--uXRc++AX6Zs6KUB1hPbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

On Fri, Sep 8, 2023 at 2:48 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> +1 to your proposal of using a struct for the entries in the cache.

Cool, I'll push/back-patch after 16.0. Even though this seems
simple enough, it's an extremely low probability failure and I'd
rather keep out of REL_16_STABLE's way...

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-09-10 22:47:35 Re: FW: query pg_stat_ssl hang 100%cpu
Previous Message Jeff Davis 2023-09-10 15:45:22 [16+] subscription can end up in inconsistent state

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Paquier 2023-09-10 22:47:35 Re: FW: query pg_stat_ssl hang 100%cpu
Previous Message Mikhail Balayan 2023-09-08 10:51:16 Planning time is time-consuming