Re: Printing backtrace of postgres processes - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Printing backtrace of postgres processes
Date
Msg-id ZdksZzw6hrxFFXO0@paquier.xyz
Whole thread Raw
In response to Re: Printing backtrace of postgres processes  (Christoph Berg <myon@debian.org>)
Responses Re: Printing backtrace of postgres processes  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
On Fri, Feb 23, 2024 at 04:39:47PM +0100, Christoph Berg wrote:
> I'd be concerned about the cost of doing that as part of the startup
> of every single backend process. Shouldn't this rather be done within
> the postmaster so it's automatically inherited by forked backends?
> (EXEC_BACKEND systems probably don't have libgcc I guess.)

Something like this can be measured with a bunch of concurrent
connections attempting connections and a very high rate, like pgbench
with an empty script and -C, for local connections.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: RangeTblEntry jumble omissions
Next
From: Michael Paquier
Date:
Subject: Re: Add lookup table for replication slot invalidation causes