Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Andersen" <david(dot)andersen(at)andersen-innovation(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5347: initdb does not work when a data directory has been deleted
Date: 2010-02-26 15:52:33
Message-ID: 27997.1267199553@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"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

In response to

Responses

pgsql-bugs by date

Next:From: David AndersenDate: 2010-02-26 16:00:00
Subject: Re: BUG #5347: initdb does not work when a data directory has been deleted
Previous:From: Greg StarkDate: 2010-02-26 15:13:51
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group