]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Assign "backend" type earlier during process start-up
authorÁlvaro Herrera <alvherre@kurilemu.de>
Wed, 4 Feb 2026 15:56:57 +0000 (16:56 +0100)
committerÁlvaro Herrera <alvherre@kurilemu.de>
Wed, 4 Feb 2026 15:56:57 +0000 (16:56 +0100)
commit0c8e082fba8d36434552d3d7800abda54acafd57
tree15f08ec8b48b6f9e7a68760fd11911d5d4c903ae
parent36ead7123292c2849be9950f3e552325fad7e6b7
Assign "backend" type earlier during process start-up

Instead of assigning the backend type in the Main function of each
postmaster child, do it right after fork(), by which time it is already
known by postmaster_child_launch().  This reduces the time frame during
which MyBackendType is incorrect.

Before this commit, ProcessStartupPacket would overwrite MyBackendType
to B_BACKEND for dead-end backends, which is quite dubious.  Stop that.

We may now see MyBackendType == B_BG_WORKER before setting up
MyBgworkerEntry.  As far as I can see this is only a problem if we try
to log a message and %b is in log_line_prefix, so we now have a constant
string to cover that case.  Previously, it would print "unrecognized",
which seems strictly worse.

Author: Euler Taveira <euler@eulerto.com>
Discussion: https://postgr.es/m/e85c6671-1600-4112-8887-f97a8a5d07b2@app.fastmail.com
15 files changed:
src/backend/postmaster/autovacuum.c
src/backend/postmaster/bgworker.c
src/backend/postmaster/bgwriter.c
src/backend/postmaster/checkpointer.c
src/backend/postmaster/launch_backend.c
src/backend/postmaster/pgarch.c
src/backend/postmaster/startup.c
src/backend/postmaster/syslogger.c
src/backend/postmaster/walsummarizer.c
src/backend/postmaster/walwriter.c
src/backend/replication/logical/slotsync.c
src/backend/replication/walreceiver.c
src/backend/storage/aio/method_worker.c
src/backend/tcop/backend_startup.c
src/backend/utils/error/elog.c