Steve Stock writes:
> Looks like initdb is just a tad too strict when checking to make sure
> the data directory is empty. Yesterday I created a new data directory
> as it's own filesystem (linux ext2), it includes a lost+found directory.
It is never a good idea to let initdb loose on a directory that might
possibly have some other purpose, including that of being the root
directory of an ext2 partition. Initdb or the database system can do
anything they want in that directory, so it's not good to save lost blocks
somewhere in the middle, even if chances are low you need them. I say,
create a subdirectory.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/