David Andersen writes:
> Thank you for your answer. The error message states:
> "initdb: directory "../data" exists but is not empty"
> This is wrong. ../data does not exist
I really, really doubt that the code gets that test wrong.
Your message suggested that you might have typed ..\data when y
Hi Tom,
Thank you for your answer. The error message states:
"initdb: directory "../data" exists but is not empty"
This is wrong. ../data does not exist
It then states:
"If you want to create a new database system, either remove or empty the
directory "../data" or run initdb with an argument othe
"David Andersen" writes:
> [ initdb fails with ]
> initdb: directory "../data" exists but is not empty
> If you want to create a new database system, either remove or empty
> the directory "../data" or run initdb
> with an argument other than "../data".
This is not a bug. It's an intentional saf
The following bug has been logged online:
Bug reference: 5347
Logged by: David Andersen
Email address: david.ander...@andersen-innovation.com
PostgreSQL version: 8.4.2
Operating system: Windows 7 64-bit
Description:initdb does not work when a data directory has been
d
