Message-ID: <9d9843f378d6388b4f752f6e31b077c565a28453.camel@cybertec.at>
Subject: Re: No console output from PostgresSQL binaries on fresh windows
 install
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: tim-sandner@gmx.de, pgsql-novice@postgresql.org
Date: Wed, 28 Oct 2020 14:10:00 +0100
In-Reply-To: <004301d6ad21$1d082f50$57188df0$@gmx.de>
References: <004301d6ad21$1d082f50$57188df0$@gmx.de>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 2020-10-28 at 12:54 +0100, tim-sandner@gmx.de wrote:
> when trying to run the official PG 13 binaries on a fresh Windows 10 VM the application exists
>  immediately with exit code -1073741515 and produces no console output of any kind.

You mean "exits", not "exists", right?

> After PostgreSQL as been installed on the machine using the installer, the binaries
>  work fine, even after removing the installation again. 
> 
> The described behavior occurs on any of the executables in the /bin folder (pg_cts, initdb, pg_dump, ...).
>  I’ve tested this on multible Windows 10 Pro VM’s (Azure Vm, local VM) .
> Are there any obvious dependencies I‘m missing?

Hard to say - perhaps there was something missing in the PATH, so that
required shared libraries could not be found?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com