Skip to content

Use dynamic port handling for ProxySQL with PostgreSQL #127

Description

@ronaldbradford

Environment

  • dbdeployer version: 2.3.0
  • Go version 1.25.6
  • OS: Linux (Ubuntu 24.04)
  • PostgreSQL version: 17.1
  • ProxySQL version: 3.0.8-481-g0ef544c
  • Topology: replication --with-proxy

Describe the bug
When using with PostgreSQL, config was using MySQL ports.
Updated use and use_proxysql to use PostgreSQL non-password syntax

$  tail proxysql/data/proxysql.log
2026-05-20 17:41:13 main.cpp:1648:ProxySQL_Main_init_phase3___start_all(): [ERROR] Configuration conflict detected: Admin listener '0.0.0.0:6032' overlaps with Admin PostgreSQL listener '127.0.0.1:6032'

Steps to reproduce

./dbdeployer-2.3.1.linux deploy replication ${PG_MINOR_VERSION} --provider=postgresql --sandbox-directory=demo --with-proxysql

Expected behavior
Switched to using custom non-conflicting PostgreSQL ports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions