Re: BUG #5347: initdb does not work when a data directory has been deleted - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5347: initdb does not work when a data directory has been deleted
Date
Msg-id 29440.1267203312@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5347: initdb does not work when a data directory has been deleted  (David Andersen <david.andersen@andersen-innovation.com>)
List pgsql-bugs
David Andersen <david.andersen@andersen-innovation.com> 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 you meant
\data, or vice versa --- you might want to double check exactly which
directory you meant.  Personally I dislike using relative paths for data
directories; it's much too easy to mess up.

            regards, tom lane

pgsql-bugs by date:

Previous
From: David Andersen
Date:
Subject: Re: BUG #5347: initdb does not work when a data directory has been deleted
Next
From: Oleg Serov
Date:
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS