Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j2puO-00005K-1y for pgsql-bugs@arkaria.postgresql.org; Sat, 15 Feb 2020 05:22:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j2puM-0000gv-E0 for pgsql-bugs@arkaria.postgresql.org; Sat, 15 Feb 2020 05:22:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j2puM-0000gn-2m for pgsql-bugs@lists.postgresql.org; Sat, 15 Feb 2020 05:22:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j2puJ-0004tK-Lb; Sat, 15 Feb 2020 05:22:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 01F5MIQ3025537; Sat, 15 Feb 2020 00:22:19 -0500 From: Tom Lane To: Alexander Lakhin cc: Heath Lord , "Jonathan S. Katz" , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16259: Cannot Use "pg_ctl start -l logfile" on Clean Install on Windows Server 2012/2016 In-reply-to: <3f72f608-88ab-bd43-b7de-685c26e69421@gmail.com> References: <16259-c5ebed32a262a8b1@postgresql.org> <22619.1581702327@sss.pgh.pa.us> <98b2f7d0-9010-358a-36c9-a5b09020dd08@postgresql.org> <3568.1581710233@sss.pgh.pa.us> <7959.1581716776@sss.pgh.pa.us> <3f72f608-88ab-bd43-b7de-685c26e69421@gmail.com> Comments: In-reply-to Alexander Lakhin message dated "Sat, 15 Feb 2020 07:44:44 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25535.1581744138.1@sss.pgh.pa.us> Date: Sat, 15 Feb 2020 00:22:18 -0500 Message-ID: <25536.1581744138@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alexander Lakhin writes: >> Alexander, this was your patch to start with ... any thoughts? > Yes, it was my omission. Please look at the improved patch. > It works for me in both command prompts and still gives a meaningful > message on error. This seems basically reasonable but I'm not in a position to test it. Heath, can you see if this improves matters for you? regards, tom lane