Subject: Re: productive usage of PostgreSQL with Windows Server
To: pgsql-admin@lists.postgresql.org
References: 
 <AM0PR05MB60828507F7097170790AAF70E9BC0@AM0PR05MB6082.eurprd05.prod.outlook.com>
From: Thomas Kellerer <shammat@gmx.net>
Message-ID: <0cfae453-28f8-0fe7-bae6-8dcea61c68ac@gmx.net>
Date: Tue, 26 Jan 2021 14:30:28 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23)
 Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
In-Reply-To: 
 <AM0PR05MB60828507F7097170790AAF70E9BC0@AM0PR05MB6082.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Dirk Krautschick schrieb am 26.01.2021 um 12:20:
> I am aware and I always surely recommend Linux but the matter of fact th=
at there
> are also customers with more Windows knowledge inhouse I always get the =
question
> about experience and references which I cannot provide at this time.
>
> Regarding the build farm status I see that it is pretty much tested and =
suppported at
> least. But I am interessted in fundational opinions and expierences.

I think the biggest drawback is that many useful tools and extensions are =
only
available on Linux. For some tools, it might be possible to compile them o=
n Windows,
but it's not as easy and straightforward as doing that on Linux.

Your choice of e.g. backup tools (beyond the built-in tools) is also limit=
ed. I think
the only one is pgProBackup - at least it contains information on how to c=
ompile
it on Windows.

In my experience, NTFS on Windows doesn't perform as good the alternatives=
 on Linux,
so performance on identical hardware is probably a bit lower when using Wi=
ndows.

Thomas