database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-24 10:47:04 +03:00
Code

Adjust obsolete comment explaining set_stack_base().

Browse Source 
Commit 7389aad6 removed the notion of backends started from inside a
signal handler.  A stray comment still referred to them, while
explaining the need for a call to set_stack_base().  That leads to the
question of whether we still need the call in !EXEC_BACKEND builds.
There doesn't seem to be much point in suppressing it now, as it doesn't
hurt and probably helps to measure the stack base from the exact same
place in EXEC_BACKEND and !EXEC_BACKEND builds.

Back-patch to 16.

Reported-by: Heikki Linnakangas <hlinnaka@iki.fi>
Reported-by: Tristan Partin <tristan@neon.tech>
Reported-by: Andres Freund <andres@anarazel.de>
Discussion: https://postgr.es/m/CA%2BhUKG%2BEJHcevNGNOxVWxTNFbuB%3Dvjf4U68%2B85rAC_Sxvy2zEQ%40mail.gmail.com
This commit is contained in:
Thomas Munro 2023-12-01 14:58:40 +13:00
parent f93133a250
commit 3b51265ee3
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/utils/init/miscinit.c
View File

@ -107,9 +107,8 @@ InitPostmasterChild(void)
/*
* Set reference point for stack-depth checking. This might seem
* redundant in !EXEC_BACKEND builds; but it's not because the postmaster
* launches its children from signal handlers, so we might be running on
* an alternative stack.
* redundant in !EXEC_BACKEND builds, but it's better to keep the depth
* logic the same with and without that build option.
*/
(void) set_stack_base();