yugabyte/yugabyte-db

[YSQL] pgsql_proxy_bind_address=127.0.0.1:5434,127.0.0.2:5436 results in PG crash

Open

#28,643 建立於 2025年9月19日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)C (8,229 star) (1,003 fork)batch import
area/ysqlgood first issuekind/bugpriority/mediumstatus/awaiting-triage

描述

Jira Link: DB-18336

Description

This tserver gflag is being transformed to the PG listen_addresses and port parameter. PG only supports a single port in its listen specification, so the above specification should be rejected as invalid. Instead, a mix of ports is used to start PG and create the socket path, causing PG to fail startup.

https://www.postgresql.org/docs/current/runtime-config-connection.html#:~:text=Note%20that%20the%20same%20port%20number%20is%20used%20for%20all%20IP%20addresses%20the%20server%20listens%20on

Issue Type

kind/bug

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

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

貢獻者指南

技術棧
ccppsql
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic understanding of PostgreSQL configurationFamiliarity with C/C++ codebase
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate how `pgsql proxy bind address` is parsed and transformed into PG's `listen addresses` and `port` parameters. Look for validation logic that should reject multiple ports. Relevant files may include those in `/yb/ysql` or `/src/postgres` that handle gflag to PG parameter conversion. Review the linked Jira for additional context.