Re: No console output from PostgresSQL binaries on fresh windows install

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: tim-sandner(at)gmx(dot)de, pgsql-novice(at)postgresql(dot)org
Subject: Re: No console output from PostgresSQL binaries on fresh windows install
Date: 2020-10-28 13:10:00
Message-ID: 9d9843f378d6388b4f752f6e31b077c565a28453.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Wed, 2020-10-28 at 12:54 +0100, tim-sandner(at)gmx(dot)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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message tim-sandner 2020-10-28 13:42:49 RE: No console output from PostgresSQL binaries on fresh windows install
Previous Message tim-sandner 2020-10-28 11:54:37 No console output from PostgresSQL binaries on fresh windows install