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 1t8Jsp-003Qjh-Jg for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 13:46:10 +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 1t8Jsl-00DaAp-No for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 13:46:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8Jsl-00DaAe-Au for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 13:46:07 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8Jsg-000KOG-No for pgsql-general@postgresql.org; Tue, 05 Nov 2024 13:46:07 +0000 Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-43155afca99so40056425e9.1 for ; Tue, 05 Nov 2024 05:46:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730814362; x=1731419162; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=g/5ytQ5AfEHDwJlZXkbqwoBcCuy5GvUPzPmR4Hk0MWw=; b=OYOGha8lOC5yyA+kuSW1L8fglByt/9NinrY0ALUM2kIGH5IXsKmwaVgZ4fCsMgfWGs kR5blDS5se/W30GDyb//WUZcKBhg3Ej2oxfh2jZLQScZxwAC0zkikIvHENhb29CyC17/ AUBLJEvyFGqLCORgL/ueDgz1UatA6xaFagdcezDpQeaEEeaq2YqPWBL0Qwt6Re3DHp5J qRPBiChqu0tTwGgKNs+viH+QOhdzZOxZXSm+CCRF0oIKDc1ZYOf+3BR3m3i47wvbNkhw 4mLmvWyUQjCTW9/kW3A0tFjDzePO4Z9aACrxLkX0q3RA1Q8oy/BKIyZ/3Rc6X/8Ddhes Fb8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730814362; x=1731419162; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=g/5ytQ5AfEHDwJlZXkbqwoBcCuy5GvUPzPmR4Hk0MWw=; b=jZNwpttNxVEYhNKC+HElgz8rrbs1c5Wlqr/RA3Sr67AJPZD7yOKPvlY+8ZAnxu5k29 UmZAW9SgHzoCEcyTuRcBBQfgmXqVh0YczbxEWAAbs+MIddJR41myDUH/A2TVX8wHrLkw QkxdFfEgRSMJxQUtEbeCRxjFypbAGBlMBTsD9mj6EXN9/HeDajTjfs6UP+QPTBefzGCK U+T4r4u0yFJMIGfUjpV3XcNp2ezq95trlTjbK2IzMz2VwSxxYnrQIymYgFqskmreAKiY SBGyIJmDNE2Ee+Ykg0A6sKJlrC9h340coPqeG6KTeRhiHQ8CnLK5APiwP9BpbL9pN2jt UEww== X-Gm-Message-State: AOJu0Yz7Q2/t0BUfBocqhXf4sg4nVSSpaJYrCKDD0/KOmRtiDyBBgUB/ pN7Axzw/dv6gTIBsX0qTSMdJN99as3n9RlZOhxMgqVmlJ8T9OIlE/2SPUAPg0aVUtrDruY4dAx3 m+1bMM3osOD4xHM6Vo756i1Yw4vCLXg== X-Google-Smtp-Source: AGHT+IFI+KRyKmYj5bgnmhrkKwARRnW+ulbxC1AMHmvpcvqpaWKurlwoNxHu/Sgw/KvSdFUNu66TgtMJyQn8w/I44uA= X-Received: by 2002:a05:6000:2a2:b0:376:dbb5:10c2 with SMTP id ffacd0b85a97d-381c14ef2afmr16184958f8f.29.1730814362034; Tue, 05 Nov 2024 05:46:02 -0800 (PST) MIME-Version: 1.0 From: Kal Date: Tue, 5 Nov 2024 19:15:51 +0530 Message-ID: Subject: Postgres listens on random port To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000038ac3b06262a9fa4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000038ac3b06262a9fa4 Content-Type: text/plain; charset="UTF-8" Hi I have a scenario in which postgres listens on a random port different from the one which was specified in pg_ctl start command. This occurs in windows. When postgres is started on port 5460, the logs denote that postgres is started on 5460. But the database actually listens on some random port like 20011 When the same postgres is started as a service,it listens on the intended port. I have tried with both normal and admin users. Any suggestions on this behaviour will be helpful. Regards Kal --00000000000038ac3b06262a9fa4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi=C2=A0

I have a scenario in = which postgres listens on a random port different from the one which was sp= ecified in pg_ctl start command.

This occurs in windows. When postgres is started on port 5460, th= e logs denote that postgres is started on 5460. But the database actually l= istens on some random port like 20011

When the same postgres is started as a service,it listens on = the intended port.

I hav= e tried with both normal and admin users.

=
Any suggestions on this behaviour will be helpful.=C2=A0<= /div>


Regards=C2=A0
Kal
--00000000000038ac3b06262a9fa4--