CODEWITHSUNDEEP
postgresqlenterprisedbdatadirectorypg-catalogpostgresql-16
dan-kli
dan-kli

Reputation: 887

Why does the PostgreSQL 16.0 EDB installer fail when using its own generated data folder for installation?

We are using the recently released PostgreSQL 16 Windows x86-64 installer to automatically install PostgreSQL 16.0 on our customer systems via a script. The installation works fine the first time. After running the generated uninstaller, it leaves behind the data folder. Running the same installer again now, it seems to have problems with that data folder and displays the following error message:

The existing data directory (catalog version: 202307071) is not compatible with this server (catalog version: PG_CATALOG_VERSION).

Screenshot from the GUI:

enter image description here

What problems does the PostgreSQL installer have with the data folder it just generated? I tried this on several machines, as well as on a completely blank VM, always the same error. Trying the same with the previously released PostgreSQL 15.4 installer works fine.

Upvotes: 0

Views: 787

Answers (1)

dan-kli
dan-kli

Reputation: 887

EDB released a new installer: PostgreSQL 16.1. They fixed this issue.

Upvotes: 1

Related Questions