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 1iZbgI-00016S-DD for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Nov 2019 14:19:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iZbgF-0007kJ-HR for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Nov 2019 14:19:03 +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 1iZbgF-0007jl-1x for pgsql-bugs@lists.postgresql.org; Tue, 26 Nov 2019 14:19:03 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iZbgC-00026L-4M for pgsql-bugs@lists.postgresql.org; Tue, 26 Nov 2019 14:19:01 +0000 Received: by mail-wr1-x443.google.com with SMTP id b18so22646790wrj.8 for ; Tue, 26 Nov 2019 06:18:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=yI4j6AY/lM/kf5eDBTY3n1y/8xxK4HX7AM8iz8Am7uc=; b=Z7BmzSVJgt4E4og0C8+UYxKhk3Z6TaVT7DNCqOTyTqNesKkNY5MWZkYHosnsX3aiWw hpAqPdP/nmh07UVo35tlQ8Nns+ADHUquf5LOyq3lrn/WwJntHiienulA8XsTvzTHT/X8 s+CmjJ52Z1xyuUvPj/o/ttnPv2iZ8dOm37q03DdRiJV7/ndzgBFScWsbwg8yDrV/GfR/ dHl4KL8iUxwtQPezysUGhCZrXjW3n3ssNNU5J+ZQb8uqvNEH5x96h9vZqwJd+kKtTVKR pTne/qI9Twmvhg5D4vzxXVRYAmiA4yJCPovIlXFpfbZ6CY/4KDVeiVZkMrPMq/B7Sl1L G73g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=yI4j6AY/lM/kf5eDBTY3n1y/8xxK4HX7AM8iz8Am7uc=; b=RKVLk32FuXBZo0VbNxOLSrmTbnK/tlOtbxIhd7TYgK6ycPx4wN4FksHzca+P2I0TfM pJFdVL1Ml9rA969Zg7JjgTylhcxRioG7yt6avR027L5FOcMkUg6gLINb2S7+fNi46eC5 YYe/Ckp2yo9vZaY+MEVOkgbllabSVhZAkczfcDJZFE2EtPyxp2pUJA6Vlb+LSgja84/u M9Qrzr5eBTZiUC7c5YxymsVqzwfIMTs2NAQFcznMcSUZGs/baz8vUnm9oE1tWt/48Utg 2vcd+qq609kGBGHx/rd7j2otMhVEWrIZE9WkNFW50ymJspmvOwmmblxdhsKv5q/bKodu /+0w== X-Gm-Message-State: APjAAAVjqFEKkF04fySOmtMdf8UgumseA1O6uH4BMhrrpMLevRgkcw+G hcJbtL91sOZ2vb0xfbjcQJQIig== X-Google-Smtp-Source: APXvYqzXBqJUzlzctH/VdXOyUHArszfuix6JDBJfLUJBEs0F+qdbVh8/gq0p1DlxFKUpZZq1+eUVGA== X-Received: by 2002:adf:f5cb:: with SMTP id k11mr32640026wrp.82.1574777937569; Tue, 26 Nov 2019 06:18:57 -0800 (PST) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id e16sm15012429wrj.80.2019.11.26.06.18.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Nov 2019 06:18:56 -0800 (PST) Date: Tue, 26 Nov 2019 15:18:54 +0100 From: Tomas Vondra To: abhilash.mishra.10@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16138: Error while installing PostgreSQL Message-ID: <20191126141854.tk3igdkdrbnskv7t@development> References: <16138-53e55839ce0c6d1d@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <16138-53e55839ce0c6d1d@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Nov 26, 2019 at 12:34:20PM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16138 >Logged by: Abhilash Mishra >Email address: abhilash.mishra.10@gmail.com >PostgreSQL version: 12.1 >Operating system: Windows >Description: > >I'm trying to install postgres on my system (on windows 10 OS) but at the >end of the installation, I'm receiving the following error message "Problem >running post-install step. Installation may not complete correctly. The >database cluster initialisation failed." > It's not clear which installer are you using (most likely the one from EDB linked from https://www.postgresql.org/download/windows/, right?). Anyway, the installer certainly produces some sort of install log which should provide much more detail about the failure. It's impossible to really help you with just the information you provided, so please search for the log, I'd expect it in %TEMP% or similar location. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services