Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8KSB-003UHZ-BM for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 14:22:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t8KS8-00Dxzt-L0 for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 14:22:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8KS8-00DxzE-8a for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 14:22:40 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8KS6-000JV5-Az for pgsql-general@postgresql.org; Tue, 05 Nov 2024 14:22:39 +0000 Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-4315e62afe0so47344725e9.1 for ; Tue, 05 Nov 2024 06:22:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730816557; x=1731421357; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6vK3LFsvhIt1KhFgpEq1Jo71ZefG6m1QcvdW0l29Kwg=; b=CaTBqrs7aPBxDR5kWBw7fwKbwpVnPdvacP/yFAagnzvAz+SC4/21kTy/m0aWA7M2tY 3cQ8X9vI7QSVK8RxXRxmqcocX9rXd7nWoeaICrkj/y0Nc2mDY+Hg+VI8/HEHPgR1MFmw bO7QpSTcQQG41zQ8KMr4TmeL4ZPqmq5oo1YrM5/Q5hCNoWzp0b4GQDAD0gtOV/fBZLp2 v+k3sWXt8kdQsaHxyVvoL8QIZ6xQkYUC53hlEBOJElyJ7beqDiw5U/q8k3bvx+W5MpY+ +soS1wu5yo1qJMYjH0ho/rFowO0X8rTsqeyxVagpCTWZY6CEtyyMNKFmWUaX+BjypeQO aGpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730816557; x=1731421357; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6vK3LFsvhIt1KhFgpEq1Jo71ZefG6m1QcvdW0l29Kwg=; b=gJrJom+Yc+I38QdeHb7iZWMbUJE7ehExW6sDa6z1DC+s8t2bRlLifu6BbI3Id5dykN DfJzjBtGsrpGXNYWFv3BZs7jmPa/vyudv639nYNcysqYtwD3EDGE6rv2y2vyHx6tUiqv e4lPs7ZKAOKBDxhul1ae1bKoSWk2MqxfcGOcpBbBPMuxiO3l/wF6GMjCSv93SpT5Y5Li RcwT0Pb6sZK1fEt4TBaoIKdELJ/NLOBUnPwgZdq9PTGE4pnSQ+P9XxfKO3S7BOUWZdNe Er3gFLZptdolAmSGfXqjdFoyh0JWABUpJ2+VfeoKeSTLA795jg21j2mzgF1A47DSi0Nm TWaA== X-Gm-Message-State: AOJu0Yz/bLEdrLGKMW+nQQ0Km3s3qDTSKVLRmRUj72RxorGhHgQN6EnM GBiSBU8UiNxx1M/bnAsdkzDTqVQGFoRrWuHU0p9afKLoLa8s48pSPTW0DH9SVAslc/U0AKAKF0n 1bnsmKOKIkpphJibRWq5ZP8Oo+vc= X-Google-Smtp-Source: AGHT+IEjaS7aV8IgyfCTyqQqILSzQqRqigmFw/g+HGmYfH9fyvIUHdTiMeK2Bv+OvdqdqWEipESHFDSJY6QmbOCaFuw= X-Received: by 2002:adf:e287:0:b0:37d:480f:9a6c with SMTP id ffacd0b85a97d-3806115883cmr22666564f8f.25.1730816556682; Tue, 05 Nov 2024 06:22:36 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kal Date: Tue, 5 Nov 2024 19:52:23 +0530 Message-ID: Subject: Re: Postgres listens on random port To: Greg Sabino Mullane Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000000855e406262b22ae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000855e406262b22ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 5 Nov 2024 at 7:42=E2=80=AFPM, Greg Sabino Mullane wrote: > Start by seeing where the port is actually being set by running this: > > select setting, source, sourcefile, sourceline from pg_settings where nam= e > =3D 'port'; > Cheers, > Greg > > Hi Greg, The query output states the source as command line. Event the port value output from show port is same as given in pg_ctl command. But the database is listening on some other random port. Regards Kal --0000000000000855e406262b22ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, 5 Nov 2024 at 7:42=E2=80=AFPM, Greg Sabino Mullane = <htamfids@gmail.com> wrote:=
Start by seeing where the port = is actually being set by running this:

select setting, s= ource, sourcefile, sourceline from pg_settings where name =3D 'port'= ;;
Cheers,
Greg

Hi Greg,
=
The query output states the source as command l= ine. Event the port value output from show port is same as given in pg_ctl = command.

But the databas= e is listening on some other random port.

=

Regards
Kal
--0000000000000855e406262b22ae--