Re: BUG #16310: Database Cluster Initialization failed while installing postgres

On Sun, Mar 22, 2020 at 01:53:49AM -0700, David G. Johnston wrote:
> On Sunday, March 22, 2020, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>
> > The following bug has been logged on the website:
> >
> > Bug reference: 16310
> > Logged by: Aniket Yadav
> > Email address: aniketyadav5757(at)gmail(dot)com
> > PostgreSQL version: 11.7
> > Operating system: Windows
> > Description:
> >
> > After downloading the stable version of postgres i.e 11.7 and installing
> > the
> > same, The database cluster initialization fails at the post installation
> > step and this disables to create servers or any databases and use postgres.
> > After i started searching for solutions for the same problem, I got to know
> > that postgres has this MAJOR problem while installation for many times.
> > So I please request you to look after this problem as it causes many issues
> > for users who believe postgres database is one of the best sql databases to
> > use.
> > Kindly resolve the same.
> >
>
> The many people who get it to work don’t report that fact. And then the
> ones that have issues give zero details which makes actually identifying a
> common cause to fix, beyond human error or failure to follow installation
> instructions, difficult. Also, the PostgreSQL project proper, which this
> list is for, doesn’t actually provide an installer. Whomever did provide
> your installer needs to provide the assistance.
>
> Maybe as you seem to have done research on the topic you can compile some
> data as to what errors people are getting and how they get resolved, and
> then include the details of your error as well. That level of additional
> follow-through seems reasonable when asking free support on a free to use
> product. Because, in all likelihood, there is no software bug here, or if
> there is its a subtle one given how many people do use the product
> successfully (admittedly more use Linux than Windows, myself included).

Correct, and this class of issue is usually caused by 3rd party software like
antivirus. In any case OP should complain to the original package author.