From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: POC: GUC option for skipping shared buffers in core dumps |
Date: | 2020-02-10 21:03:31 |
Message-ID: | 20200210210331.hhdqrhk4ontzaxhg@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2020-02-10 17:31:47 -0300, Alvaro Herrera wrote:
> Yeah. Maybe we should file bug reports against downstream packages to
> include a corefilter tweak.
Hm, I'm not sure that's a reasonable way to scale things. Nor am I
really sure that's the right granularity.
> My development helper script uses this
>
> runpg_corefilter() {
> pid=$(head -1 $PGDATADIR/postmaster.pid)
> if [ ! -z "$pid" ]; then
> echo 0x01 > /proc/$pid/coredump_filter
> fi
> }
>
> I don't know how easy is it to teach systemd to do this on its service
> files.
Well, you could just make it part of the command that starts the
server. Not aware of anything else.
> FWIW I've heard that some people like to have shmem in core files to
> improve debuggability, but it's *very* infrequent.
Oh, I pretty regularly want that. If you're debugging anthying that
includes locks, page accesses, etc, it's pretty hard to succeed without?
> But maybe we should have a way to disable the corefiltering.
There should, imo. That's why I was wondering about making this a GUC
(presumably suset).
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-02-10 21:21:30 | Re: POC: GUC option for skipping shared buffers in core dumps |
Previous Message | Alvaro Herrera | 2020-02-10 20:31:47 | Re: POC: GUC option for skipping shared buffers in core dumps |