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
This commit is contained in:
parent
e2e3b8ae9e
commit
a3f349c612
|
@ -5741,7 +5741,7 @@ do_start_bgworker(RegisteredBgWorker *rw)
|
||||||
case -1:
|
case -1:
|
||||||
/* in postmaster, fork failed ... */
|
/* in postmaster, fork failed ... */
|
||||||
ereport(LOG,
|
ereport(LOG,
|
||||||
(errmsg("could not fork worker process: %m")));
|
(errmsg("could not fork background worker process: %m")));
|
||||||
/* undo what assign_backendlist_entry did */
|
/* undo what assign_backendlist_entry did */
|
||||||
ReleasePostmasterChildSlot(rw->rw_child_slot);
|
ReleasePostmasterChildSlot(rw->rw_child_slot);
|
||||||
rw->rw_child_slot = 0;
|
rw->rw_child_slot = 0;
|
||||||
|
@ -5853,7 +5853,7 @@ assign_backendlist_entry(RegisteredBgWorker *rw)
|
||||||
{
|
{
|
||||||
ereport(LOG,
|
ereport(LOG,
|
||||||
(errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED),
|
(errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED),
|
||||||
errmsg("no slot available for new worker process")));
|
errmsg("no slot available for new background worker process")));
|
||||||
return false;
|
return false;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue