Re: BUG #5347: initdb does not work when a data directory has been deleted

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 other than "../data".
The first part of this sentence is what I attempted to do, and it did not
work.

Regards,

David

On Fri, Feb 26, 2010 at 16:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David Andersen" <david(dot)andersen(at)andersen-innovation(dot)com> 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 safety feature to prevent people
> from accidentally wiping out their databases by re-initdb'ing over them.
> If you really want to re-initdb, do what the message tells you to.
>
> regards, tom lane
>