From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Use a signal to trigger a memory context dump? |
Date: | 2014-06-23 10:15:01 |
Message-ID: | 20140623101501.GN16260@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I wonder if it'd make sense to allow a signal to trigger a memory
context dump? I and others more than once had the need to examine memory
usage on production systems and using gdb isn't always realistic.
I wonder if we could install a signal handler for some unused signal
(e.g. SIGPWR) to dump memory.
I'd also considered adding a SQL function that uses the SIGUSR1 signal
multiplexing for the purpose but that's not necessarily nice if you have
to investigate while SQL access isn't yet possible. There's also the
problem that not all possibly interesting processes use the sigusr1
signal multiplexing.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2014-06-23 10:15:39 | Re: pgaudit - an auditing extension for PostgreSQL |
Previous Message | Andres Freund | 2014-06-23 10:07:34 | Re: crash with assertions and WAL_DEBUG |