You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Rename some signal and interrupt handling functions for consistency
The usual pattern for handling a signal is that the signal handlersets a flag and calls SetLatch(MyLatch), and CHECK_FOR_INTERRUPTS() orother code that is part of a wait loop calls another function to dealwith it. The naming of the functions involved was a bit inconsistent,however. CHECK_FOR_INTERRUPTS() calls ProcessInterrupts() to do theheavy-lifting, but the analogous functions in aux processes werecalled HandleMainLoopInterrupts(), HandleStartupProcInterrupts(),etc. Similarly, most subroutines of ProcessInterrupts() were calledProcess*(), but some were called Handle*().To make things less confusing, rename all the functions that are partof the overall signal/interrupt handling system but are not executedin a signal handler to e.g. ProcessSomething(), rather thanHandleSomething(). The "Process" prefix is now consistently used inthe non-signal-handler functions, and the "Handle" prefix in functionsthat are part of signal handlers, except for some completely unrelatedfunctions that clearly have nothing to do with signal or interrupthandling.Reviewed-by: Nathan Bossart <nathandbossart@gmail.com>Discussion:https://www.postgresql.org/message-id/8a384b26-1499-41f6-be33-64b801fb98b8@iki.fi