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

Re: initdb: directory not empty issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeffrey Quinn <jquinn(at)cs(dot)usfca(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: initdb: directory not empty issue
Date: 2004-01-31 00:56:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Jeffrey Quinn <jquinn(at)cs(dot)usfca(dot)edu> writes:
> The problem, however, is that this will fail if I am trying to enable a 
> separate filesystem as the data location.  It's rather annoying to have 
> to remove a lost+found directory (or other files), init the db, and then 
> remake lost+found (and restore other files).  How about a --force 
> flag?

Why not create a /data directory just below the filesystem root, and use

I believe it's generally considered that root should own filesystem
mount points, so using a filesystem root directory directly as the PG
data directory seems like bad practice.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-01-31 04:08:09
Subject: Re: FW: Can not always connect to postmaster. Sometimes get "Connection refused".
Previous:From: Orion HenryDate: 2004-01-30 23:35:14
Subject: segfault in psql on x86_64

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