Skip to main content
Commonmark migration
Source Link

Manually creating a DB cluster solved it in my case.

For some reason, when I installed postgres, the "initial DB" wasn't created. Executing initdb did the trick for me.

This solution is provided in the PostgreSQL Wiki - First steps:

initdb

 

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb

Manually creating a DB cluster solved it in my case.

For some reason, when I installed postgres, the "initial DB" wasn't created. Executing initdb did the trick for me.

This solution is provided in the PostgreSQL Wiki - First steps:

initdb

 

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb

Manually creating a DB cluster solved it in my case.

For some reason, when I installed postgres, the "initial DB" wasn't created. Executing initdb did the trick for me.

This solution is provided in the PostgreSQL Wiki - First steps:

initdb

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb

update link, minor edits
Source Link
Erwin Brandstetter
  • 668.5k
  • 160
  • 1.2k
  • 1.3k

Manually initialize the startercreating a DB cluster solved it, in my case.

Executing initdb did the trick for me.

For some reason, when I installed postgres, the "initial DB" wasn't created. Executing initdb did the trick for me.

In order to solve the problem, this is theThis solution is provided forin the postgreSQL wikiPostgreSQL Wiki - First steps.:

initdb

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdbrun initdb

Manually initialize the starter DB solved it, in my case.

Executing initdb did the trick for me.

For some reason, when I installed postgres, the "initial DB" wasn't created.

In order to solve the problem, this is the solution provided for the postgreSQL wiki - First steps.

initdb

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb

Manually creating a DB cluster solved it in my case.

For some reason, when I installed postgres, the "initial DB" wasn't created. Executing initdb did the trick for me.

This solution is provided in the PostgreSQL Wiki - First steps:

initdb

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb

Source Link
Natacha
  • 1.3k
  • 19
  • 27

Manually initialize the starter DB solved it, in my case.

Executing initdb did the trick for me.

For some reason, when I installed postgres, the "initial DB" wasn't created.

In order to solve the problem, this is the solution provided for the postgreSQL wiki - First steps.

initdb

Typically installing postgres to your OS creates an "initial DB" and starts the postgres server daemon running. If not then you'll need to run initdb