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 1tEAJj-005cKH-4M for pgsql-general@arkaria.postgresql.org; Thu, 21 Nov 2024 16:46:07 +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 1tEAJh-00HNfr-R8 for pgsql-general@arkaria.postgresql.org; Thu, 21 Nov 2024 16:46:05 +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 1tEAJh-00HNfj-GF for pgsql-general@lists.postgresql.org; Thu, 21 Nov 2024 16:46:05 +0000 Received: from fhigh-b6-smtp.messagingengine.com ([202.12.124.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEAJe-0038Pu-KH for pgsql-general@lists.postgresql.org; Thu, 21 Nov 2024 16:46:04 +0000 Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfhigh.stl.internal (Postfix) with ESMTP id CD89E2540181; Thu, 21 Nov 2024 11:46:00 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-11.internal (MEProxy); Thu, 21 Nov 2024 11:46:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1732207560; x=1732293960; bh=XTJg01hZTDce9yCfhcJLvQP/d+9KD6/+EpKgkaYB8FE=; b= e8LO8/6p6UNjtwdFPbdzzbxCT31f+CcCpcbr1j0vcZbRfXp/nLzM8hxg71/c3SJj li9dcp/+ZUca7X6bxi7t2hGdZLgrUSGTmqbwizLSpiUfhXdQipGSsH4KtLYt+c7B SvVGyDGGilb4tfqtqi8dPlHIRKbJK8l9uyiU2B/PMHzR0cq3AOvF9eCNndxUekL0 MYUNDLw3PqoXcMNHgxBEL+gBuJCULaTcPjKq2wXa5bAVzPWZMUjhnEqZmGjpgYtt OFACyWYKsuCUUKlxfDoTdI2oh2StPRLnsO5TS2vpcrRaQKOJIr7WcyYCVbJMw1n7 WJHbwksu9kzgHtDsICrG6g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1732207560; x=1732293960; bh=X TJg01hZTDce9yCfhcJLvQP/d+9KD6/+EpKgkaYB8FE=; b=UtZng0iEBurrPZqF+ F7QswjLG89GBSDEmTmYzWhXG8xCnkbeM9bxv8XA10KvaNAUi98eYwwABS4UOWoIi ImMxbpsnMJND5c1u0vDG6K5lwsIljkMb7mAlp+bIcpMGesd1iUfKL8VvneU0Rjmj 4/IzjVg9NDYmSmoibTV78pY5uWtdzj+epFPbPyx60w/Z1Ue7fVztPeWGBTqEMI89 f3PIvq+cFpRNq78nMyyVKrG1yfUvr+pW2Xi4Rmmm6PooMJNW2qC9aV7RMiATIwxw gKdyR6EgDjJmnPcKOzfuyb3//v1kbyCROoG5aQhrgPTzhzfWmkWGlYSSzypXFwf5 ABjXw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrfeeigdeltdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdejnecu hfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrg hklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepkeefhfffgfelgfejheehleeh vdegffefleffvdevtdeiffeuhfeivdevtdelhfejnecuffhomhgrihhnpehgihhthhhusg drtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtth hopedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehtshgthhifvghikhhlvges sghfshdruggvpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlheslhhishhtshdrph hoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 21 Nov 2024 11:45:59 -0500 (EST) Message-ID: Date: Thu, 21 Nov 2024 08:45:58 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Postgres service not starting on windows after install if not installed into standard locations To: Thomas Schweikle , "pgsql-general@lists.postgresql.org" References: <054ffbb250c1ea1713b0e9e91d038a4a9071fc94.camel@cybertec.at> <44c72245-7cb5-47bd-a6b5-e15d0b2a487e@bfs.de> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/21/24 06:10, Thomas Schweikle wrote: > Am Mi., 20.Nov..2024 um 18:15:42 schrieb Adrian Klaver: >> On 11/20/24 05:26, Thomas Schweikle wrote: >>> Am Mo., 18.Nov..2024 um 19:43:36 schrieb Laurenz Albe: >>>> On Mon, 2024-11-18 at 17:22 +0000, Thomas Schweikle wrote: >>>>> Had installed PostgreSQL 16.5 on Windows 10: >> Did you change settings during the install? > > I called the installer with: > > .\postgresql-16.5-1-windows-x64.exe > > Then changed install path to: "C:\PRGS\pgSQL" > And database path to: "C:\DB\pgSQL" > > After a while postgres got installed into "C:\PRGS\pgSQL\16" and the > database path was created: "C:\DB\pgSQL\16\data", but the database was > not created. Calling pg_initdb did the job and created the database > within the given folder. > > Calling "pg_ctl start" gave a message, that "pg_ctl.exe" could not find > "postgres.exe" -- I prepended "C:\PRGS\pgSQL\16\bin" to %PATH%. Next > thing was that pg_ctl could not find the just, with pg_initdb, created > database. So I've set up PGDATA to point to "C:\DB\pgSQL\16\data". Both > within the global system environment of windows. > > Tried again to start postgres via "pg_ctl start". This time postgres got > up and running instantly. > > Then stopped postgres again: "pg_ctl.exe stop". And tried it using "net > start postgresql-x64-16". This failed. "pg_ctl.exe" called could not > find "postgres.exe". > > Looking at the logs "pg_ctl.exe" stated it could not find "postgres.exe" > again. Since %PGDATA% and %PATH% where set within system environment > these are to be global and shall be active for services too. > > Looking closer on "pg_ctl.exe" I found it using a build in path of > "C:\Program files\PostgreSQL\16\bin\postgres.exe", regardless of any > environment variables set if started without any of stdout, stdin, > stderr, what is the case if it is started as a service. > Looks like your choices are: 1) Keep the default paths during the install. 2) Raise an issue here: https://github.com/EnterpriseDB/edb-installers/issues -- Adrian Klaver adrian.klaver@aklaver.com