Jeffrey Quinn <[EMAIL PROTECTED]> 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 restor
Hi,
Don't know if this is a bug or more of a feature request, but here goes:
It would appear that by default initdb refuses to configure a database
within a directory that already contains files/directories. I understand
that this is desirable in most cases.
The problem, however, is that
