Message-ID: <bff158664080ece17cf82ef861886dce2e4a4748.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 16:38:34 +0100
In-Reply-To: <000501d6ad30$3aafe610$b00fb230$@gmx.de>
References: <004301d6ad21$1d082f50$57188df0$@gmx.de>
	 <9d9843f378d6388b4f752f6e31b077c565a28453.camel@cybertec.at>
	 <000501d6ad30$3aafe610$b00fb230$@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: 7bit
Precedence: bulk

On Wed, 2020-10-28 at 14:42 +0100, tim-sandner@gmx.de wrote:
> > Hard to say - perhaps there was something missing in the PATH, so that required shared libraries could not be found?
>
> Have you got any idea where I would find more information on that? I not able to find anything but the build dependencies on the topic.
> If not, I might have to consider another way of implementing PostgreSQL as a backend for my application. (possibly a headless installer)

I guess you don't find anything about that in the installation section because it
is operating system specific.

PostgreSQL does not consist of statically linked monolithic executables, but
it requires shared libraries for its operation (DLL in Windows).

The required shared libraries are included in the binary Windows distribution.
But you have to configure the shared library search path, otherwise Windows
won't find the shared libraries.  On windows, the PATH environment variable
doubles as shared library search path.

Ask your system administrator or perform a web search about PATH on Windows.

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