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 1iCKJk-00047z-JM for pgadmin-support@arkaria.postgresql.org; Mon, 23 Sep 2019 09:07:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iCKJi-0007GQ-BD for pgadmin-support@arkaria.postgresql.org; Mon, 23 Sep 2019 09:07:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iCKJi-0007GG-0X for pgadmin-support@lists.postgresql.org; Mon, 23 Sep 2019 09:07:34 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iCKJg-0000ZQ-BO for pgadmin-support@lists.postgresql.org; Mon, 23 Sep 2019 09:07:33 +0000 Received: by mail-wm1-x341.google.com with SMTP id v17so8364538wml.4 for ; Mon, 23 Sep 2019 02:07:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=LLklM81gYweOtKuYtNngmCnPesa6I3mZrxsvIdQNcJg=; b=lehzcUcOqrt6rq6oarc+QBslCY1qCN3caq54cayGyBoMbCKtO9RcMq0ImwiXStgajY +SGCQyiW9rZyOnv6hxrqLjSU6QJ5fT411p73eDp/CyaUq6Z+amTVm++hZwr0hNvi3apf 8BkkVqxYk2I1Vs7p1Vkz2Nm2fLhNn9xcvMkjUgR4cDnjeIa5lmGpQpHdmJsAZDIaJPHC +BimDhfkfzx3WijaWRZ581KBWelBmVHLyDvflpF0PDiwjDCQpVjs27eM5QcS7CKJAYlC qlI+7az7qBoqLUYd5OzKqSqp4Vxrg/ccLAWXVq3q18FmgkCJaJBvtTLUVayHa44Vferq B85A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=LLklM81gYweOtKuYtNngmCnPesa6I3mZrxsvIdQNcJg=; b=jzOWhxxeeoppivEgRdcnFXqXgOa1DRHmoKQgFsXJNbi/N9nb/MS/gHwm6RIW5FzUqx KEfJEF0zf+aGxk7ph40VdB2DbmT1DVO9aHn2ft7d2p3Qz/E4aOOdi4FDeyxXgwhAzBBy WudgIa891TmOKQ3SfPxystTeT4W6u2Om0cjza+yW/bBCyOIK9jT2C1Sqiuc5a086uQs3 cmcnzkLPX8v35tfGo9AMIW4r+LNWqZaKhLYx/LnY4NwQj7xdrjYv2bXPg5Xgxb61DCO0 F7r4hsvE/FDIQRMxl/TyMINGmsM/rgS73lWlWZaxVHfLTICnd7RStB5Eqg5TagU8q969 F0JA== X-Gm-Message-State: APjAAAVWAwb14bOLqiq9DpLQPLEfyr8qEzU+sGtu5blaJ578ZNmI9h8t OqEcBrA4CkZqCSRry8h6nVZTkpB8fAw= X-Google-Smtp-Source: APXvYqwBIenfCVPl6+ChVHNE+Z8MF38GVBANx4emEo8UI0GQ5QwnlBz2O5u5ukvIDjzjPjO/T06qSA== X-Received: by 2002:a05:600c:20a:: with SMTP id 10mr13924550wmi.75.1569229650749; Mon, 23 Sep 2019 02:07:30 -0700 (PDT) Received: from [192.168.0.120] (melany.rs. [178.254.155.58]) by smtp.gmail.com with ESMTPSA id v2sm20206532wmf.18.2019.09.23.02.07.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Sep 2019 02:07:29 -0700 (PDT) Subject: Re: POSTGRES ISSUES To: pgadmin-support@lists.postgresql.org References: <72C794D7-4586-4F5C-B0EA-4E55FE58479D@artsman.com> From: Milan Oparnica Message-ID: Date: Mon, 23 Sep 2019 11:07:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <72C794D7-4586-4F5C-B0EA-4E55FE58479D@artsman.com> Content-Type: multipart/alternative; boundary="------------27654465DF9EDCCC3D4270A7" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------27654465DF9EDCCC3D4270A7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I share experience with Duogh. We've installed PostgreSQL on Windows almost as much as on Linux (dozens) and had no issues on either OS. I remember once having issue similar to yours, it happened while upgrading Pg 10.1 to 10.4. New installer wouldn't recognize the database in the previous folder. Turned out to be some strange user permissions issue, which, by the way, we couldn't solve. We allowed installer to create a new folder and copied old data into. And that was it. BR, M.O. On 22.9.19. 16:26, Doug Easterbrook wrote: > I might just say that this advice is a little harsh. > > I’ve never had any problem with enterprise DB’s Postgres installers > for windows.   if you have your machine generally up todate with > latest patches and you are using 64 bit OS like win 2008 server, 2012 > server 2016 server, 2019 server, win 81. or win 10 — it basically > installs out the gate. > > I’ve never fussed with it.      I’ve ben buil my on installers around > it ..      The only parameters I give to the postgres install package are > > --mode unattended --superpassword [myPassword] --servicepassword > [myPassword] > > > > and its hardly more stock than that. [myPassword].   is a password of > my choosing.  read about the parameters  using —help as the installer > parameters. > * > **Doug Easterbrook* > *Arts Management Systems Ltd.* > mailto:doug@artsman.com > http://www.artsman.com > Phone (403) 650-1978 > >> On September 22, 2019, at 4:21 AM, Andreas Steinel >> > wrote: >> >> Hi Myke, >> >> On Fri, Sep 20, 2019 at 12:54 PM Myke Ndungu > > wrote: >> >> Hello there im in windows trying to install both postreSQL 11 a >> and Pgadmin 4 but without good progress. >> im keeping on receiving an error "database cluster not >> initialized" have used all the solutions eg >> adding postgres in computer management and giving it full rights >> on the security properties section in postgreSQL file folder >> though during reinstallation its telling me to chose another >> directory to upgrade the current application. >> i also tried to install afresh postgres using the command prompt >> still not yet >> ALSO INCLUDED THE POSTGRES PATH IN THE ENVIRONMENT VARIABLE still >> not working >> Advise from there please >> >> >> Yes, Windows and PostgreSQL are not the best friends and that's OK. >> Why don't you just go down the Docker route and stop trying to use >> Windows for PostgreSQL. >> There is no easier method to get started with both than Docker. >> >> -- >> With kind regards / Mit freundlichen Grüßen >> >> Andreas Steinel >> M.Sc. Visual Computing >> M.Sc. Informatik > --------------27654465DF9EDCCC3D4270A7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I share experience with Duogh.

We've installed PostgreSQL on Windows almost as much as on Linux (dozens) and had no issues on either OS.
I remember once having issue similar to yours, it happened while upgrading Pg 10.1 to 10.4.

New installer wouldn't recognize the database in the previous folder.
Turned out to be some strange user permissions issue, which, by the way, we couldn't solve. We allowed installer to create a new folder and copied old data into. And that was it.

BR,

M.O.


On 22.9.19. 16:26, Doug Easterbrook wrote:
I might just say that this advice is a little harsh.

I’ve never had any problem with enterprise DB’s Postgres installers for windows.   if you have your machine generally up todate with latest patches and you are using 64 bit OS like win 2008 server, 2012 server 2016 server, 2019 server, win 81. or win 10 — it basically installs out the gate.

I’ve never fussed with it.      I’ve ben buil my on installers around it ..      The only parameters I give to the postgres install package are

--mode unattended --superpassword [myPassword] --servicepassword [myPassword]



and its hardly more stock than that.   [myPassword].   is a password of my choosing.  read about the parameters  using —help as the installer parameters.

Doug Easterbrook
Arts Management Systems Ltd.
Phone (403) 650-1978

On September 22, 2019, at 4:21 AM, Andreas Steinel <a.steinel@gmail.com> wrote:

Hi Myke,

On Fri, Sep 20, 2019 at 12:54 PM Myke Ndungu <mykendoch@gmail.com> wrote:
Hello there im in windows trying to install both postreSQL 11 a and Pgadmin 4 but without good progress.
im keeping on receiving an error "database cluster not initialized" have used all the solutions eg
adding postgres in computer management and giving it full rights on the security properties section in postgreSQL file folder though during reinstallation its telling me to chose another directory to upgrade the current application.
i also tried to install afresh postgres using the command prompt still not yet
ALSO INCLUDED THE POSTGRES PATH IN THE ENVIRONMENT VARIABLE still not working
Advise from there please

Yes, Windows and PostgreSQL are not the best friends and that's OK.
Why don't you just go down the Docker route and stop trying to use Windows for PostgreSQL.
There is no easier method to get started with both than Docker.

--
With kind regards / Mit freundlichen Grüßen

Andreas Steinel
M.Sc. Visual Computing
M.Sc. Informatik

--------------27654465DF9EDCCC3D4270A7--