Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k30jo-0004HR-IU for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Aug 2020 17:28:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k30jn-0007M3-Gv for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Aug 2020 17:28:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k30jn-0007Lu-74 for pgsql-bugs@lists.postgresql.org; Tue, 04 Aug 2020 17:28:31 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k30jg-0001YR-2r for pgsql-bugs@lists.postgresql.org; Tue, 04 Aug 2020 17:28:30 +0000 Received: by mail-wm1-x343.google.com with SMTP id k20so3694846wmi.5 for ; Tue, 04 Aug 2020 10:28:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=iuFfN4KNDgYqatGFsEvBMEdc9u3Liq4c4yih+afRvxw=; b=Ll8KH3yCZewiwkCGlnUVc0/w3ahJlSyXwjmzi20Naw4zlzxDwLvcv7hEoB4D43Kve3 oXIKIUew+XWGj4AKg4Q5eABC3gxVowNvPKhsPRZ/nm8KH50wirQ4NuS2bLFRgcR+KXwW aW7YW5KDPpZ7/GBiFPeQ6tw512tFBRjU0xgtAILaOVzs781akLvL9yNQdpFnmksHwYFB dPNwBlcEMa6akBonJAVe78Bf5TZHWxdEiU59kKKZkshGTpj3KLkag1KLN4MfrzEbAg83 4lqwDsY+JJg6avoWbaNX/NPCGZPni6aZ5aDmcgbt53aJR6piHUAXDRGXqeG7996SQ6yI SokQ== 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:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=iuFfN4KNDgYqatGFsEvBMEdc9u3Liq4c4yih+afRvxw=; b=QY5dCtw6FfioxndZYyXv9YST/P65UYo8ttcPwFNTTQvunZEo/pgAV+aD4t6GsFj9JE ZPyALXuEOvuekGurkf+uglH3kON2Mhmtl0FHY6s/10EYPL/aYj+1h4IObb12O10PP0pN vuDkEmmv0Y3bjcy7l+u0SwVe/rIw/VdFXyhvjVBawja6DIdSXOwvlnu+OHr/UQhMLE3c zsh4dAKmSnUaF33jX56il7Va5w8Bm+Q3DyIkd9p8n4+arcVTM/cwCsWuSqgU++KEMW/o GfaMzf6cS95hMxs9zMcR5T4DiRY6VqQeys7E/t3S5/OPMH+zyG9EwqhjSfYtdeCtHucK h8eQ== X-Gm-Message-State: AOAM531kGs6e65RlkLNvbUjRKtLX0OV0o6yaiL4drMZGswYXypJ12Aox AmUST1wKpX6my6nnm1XDAI5M3A== X-Google-Smtp-Source: ABdhPJwPBs9PZgqDQ+aC2oTiWbjD2T5ikCrzUzVEXNTl5EG1//+kdko3ufhxkbbxvcbZupIubk0Syg== X-Received: by 2002:a1c:a513:: with SMTP id o19mr4916126wme.119.1596562102965; Tue, 04 Aug 2020 10:28:22 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id c15sm5128767wme.23.2020.08.04.10.28.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Aug 2020 10:28:22 -0700 (PDT) Date: Tue, 4 Aug 2020 19:28:19 +0200 From: Tomas Vondra To: dmitrikozlov@yahoo.com, pgsql-bugs@lists.postgresql.org Cc: Dave Cramer Subject: Re: BUG #16556: The database cluster initialisation failed - Win 10 postgresql 12.3 version installation error Message-ID: <20200804172819.2pypn45skt7hega6@development> References: <16556-06bd247db1fbc970@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <16556-06bd247db1fbc970@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Jul 27, 2020 at 12:24:09AM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16556 >Logged by: Dmitri Kozlov >Email address: dmitrikozlov@yahoo.com >PostgreSQL version: 12.3 >Operating system: Windows 10 >Description: > >Hello > >I am using Windows 10 Professional Machine at home. I have admin rights. > >I am running the installation of version 12.3 (latest) > >I am getting the error: >Problem running post-install step. Installation may not complete correctly >The database cluster initialisation failed. > >Before Installation of version 12.3, I completed the steps below: >1. Uninstalled version 11 from Apps & Features on windows 10 >2. Uninstalled pgadmin3 from Apps & Features on windows 10 >3. Deleted the folder: C:\Program Files\Postgresql >4. Downloaded version 12.3 (latest) > >The error occurred when I try to use: >1. The default installation path under C:\Program Files >2. Created new folder C:\Postgresql > >No matter what installation path folder I use, the installation always looks >at C:\Program Files >I get the error no matter what installation path I use. > >Could you please look into this issue and let me know why I cannot install >the new version or provide a workaround solution to address the problem. > >I've seen this issue reported in the past, and when I try follow the advice, >nothing seems to work. > >Therefore, I decided to create the official ticket. > Seems like a bug in getProcedureColumns(), which is missing check of the pg_proc.prokind column. getProcedures() does this if (connection.haveMinimumServerVersion(ServerVersion.v11)) { sql += " AND p.prokind='p'"; } but getProceduresColumns() does not, so it happily returns columns even for functions. Dave, does this analysis seem correct? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services