Re: Proposal for Signal Detection Refactoring - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Proposal for Signal Detection Refactoring
Date
Msg-id 20190117180824.ssrhupmcw2jf6mjn@alap3.anarazel.de
Whole thread Raw
In response to Re: Proposal for Signal Detection Refactoring  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Proposal for Signal Detection Refactoring  (Chris Travers <chris.travers@adjust.com>)
List pgsql-hackers
Hi,

On 2018-10-09 16:04:35 +0200, Peter Eisentraut wrote:
> More generally, I'd like this material to be code comments.  It's the
> kind of stuff that gets outdated before long if it's kept separate.

I'm not sure I buy this here - we don't have (but perhaps should?) a
convenient location for an overview comment around this. There's no
"signal_handling.c" where it'd clearly belong - given the lack of a
clear point to look to, I don't think a README.SIGNAL_HANDLING would get
out-of-date more quickly than code comments in mildly related place (say
postgres.c or miscinit.c) would get out of date at a different pace.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Chris Travers
Date:
Subject: Re: Proposal for Signal Detection Refactoring
Next
From: Stephen Frost
Date:
Subject: Re: ArchiveEntry optional arguments refactoring