postgres.git / summary / log / commit / refs

commit    a3f349c612923b53bd168b1dfb541a4ec712b421
Author:   Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date:     Fri Mar 15 11:14:38 2024 +0000
First released in: 17.0

    Improve log messages referring to background worker processes
    
    "Worker" could also mean autovacuum worker or slot sync worker, so
    let's be more explicit.
    
    Per Tristan Partin's suggestion.
    
    Discussion: https://www.postgresql.org/message-id/CZM6WDX5H4QI.NZG1YUCKWLA@neon.tech


 src/backend/postmaster/postmaster.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 49fc6f979e9..a8793fcb0bc 100644
--- a/src/backend/postmaster/postmaster.c
+++ b/src/backend/postmaster/postmaster.c
@@ -5741,7 +5741,7 @@ do_start_bgworker(RegisteredBgWorker *rw)
 		case -1:
 			/* in postmaster, fork failed ... */
 			ereport(LOG,
-					(errmsg("could not fork worker process: %m")));
+					(errmsg("could not fork background worker process: %m")));
 			/* undo what assign_backendlist_entry did */
 			ReleasePostmasterChildSlot(rw->rw_child_slot);
 			rw->rw_child_slot = 0;
@@ -5853,7 +5853,7 @@ assign_backendlist_entry(RegisteredBgWorker *rw)
 	{
 		ereport(LOG,
 				(errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED),
-				 errmsg("no slot available for new worker process")));
+				 errmsg("no slot available for new background worker process")));
 		return false;
 	}
 


[parent: e2e3b8ae9ed7]