On 2005-09-08, Peter Eisentraut <[EMAIL PROTECTED]> wrote: > Andrew - Supernews wrote: >> Running initdb behind the scenes is a proven dangerous practice > > Please elaborate.
Example instance: http://archives.postgresql.org/pgsql-hackers/2004-12/msg00851.php More generally, you risk running initdb and doing a normal database startup despite missing filesystems (assuming your db is substantial and important enough that you don't keep in it /var or /usr). There are a number of ways that this can bite you, whether due to thinking that the database is up when it really isn't usable, or subsequently mounting over the new data dir, or any number of other potential issues. A missing data directory on startup should mean "something is wrong", not "oh look, I'll run initdb and start up anyway". -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
