[YSQL] pgsql_proxy_bind_address=127.0.0.1:5434,127.0.0.2:5436 results in PG crash · yugabyte/yugabyte-db#28643

(3 comments) (0 reactions) (0 assignees)C (8,229 stars) (1,003 forks)batch import

area/ysqlgood first issuekind/bugpriority/mediumstatus/awaiting-triage

説明

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
Issue 種別: bug
難度: 3
推定時間: half day
活動状況: fresh
明確さ: clear
前提条件: Basic understanding of PostgreSQL configurationFamiliarity with C/C++ codebase
初心者向け度: 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.