yugabyte/yugabyte-db

[YSQL] Make postgres backend startup logs concise and useful

Open

#31833 opened on May 21, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)C (8,229 stars) (1,003 forks)batch import
area/ysqlgood first issuekind/enhancementpriority/low

Description

Jira Link: DB-21532

Description

Whenever a new backend starts up, we get the following log messages at default log level:

I0521 13:08:58.093974 4282175680 postmaster.c:5044] Started regular backend with pid: 59881, user_name: yugabyte, remote_ps_data: 127.0.0.1(62342)
I0521 13:08:58.097683 4282175680 pggate.cc:526] Using TServer host_port: 127.0.0.1:9100
W0521 13:08:58.099365 4282175680 hybrid_clock.cc:149] HybridClock initialized in local mode (OS X only). Not suitable for distributed clusters.
I0521 13:08:58.101590 4282175680 pg_client.cc:708] Session id 9: Session id acquired. Postgres backend pid: 59881

These messages come from a mix of postgres and pggate logs. The following message is redundant and can be removed:

  • Using TServer host_port: 127.0.0.1:9100: This is a constant for all backends in the node. It doesn't really add new information.

The following message can be enhanced with additional information:

  • Started regular backend with pid: 59881, user_name: yugabyte, remote_ps_data: 127.0.0.1(62342)

Specifically, the following items can be added to it:

  • Name of the database that we are connected to.
  • Name of the application as set by the user/client
  • The backend type
  • If the process is a parallel query worker, then the process ID of the parallel group leader

The following serves as a good source of documentation for this change: https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LINE-PREFIX

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Tech stack
ccpp
Domain
backenddatabaseobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PostgreSQL logging internalsC/C++ programmingYugabyteDB build system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Focus on modifying postmaster.c (line 5044) to enhance the 'Started regular backend' message by adding database name, application name, backend type, and parallel group leader pid. Remove the redundant 'Using TServer host port' log from pggate.cc (line 526). Refer to PostgreSQL docs on log line prefix for guidance. The Jira link provides additional context.