Re: atexit_callback can be a net negative

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Florian Weimer <fweimer(at)redhat(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: atexit_callback can be a net negative
Date: 2014-03-07 15:10:18
Message-ID: 15030.1394205018@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Weimer <fweimer(at)redhat(dot)com> writes:
> On 03/07/2014 03:57 PM, Tom Lane wrote:
>> It's not a reason not to do something about the much larger chance of
>> this happening in a direct child process, which certainly won't have a
>> matching PID.

> Indeed. Checking getppid() in addition might narrow things down further.

I don't think getppid adds much to the party. In particular, what to
do if it returns 1? You can't tell if you're an orphaned backend (in
which case you should still do normal shutdown) or an orphaned
grandchild. The standalone-backend case would also complicate matters.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Weimer 2014-03-07 15:13:32 Re: atexit_callback can be a net negative
Previous Message Andres Freund 2014-03-07 15:07:25 Re: atexit_callback can be a net negative