"Kevin O'Gorman" <[EMAIL PROTECTED]> writes: > I'm just catching up to the tip of the current tree, and find > that I have a reported failure in initdb. initdb works fine for me (as of CVS from about 11:30AM EST today). Try running it with -d or -v or whatever the verbose-output option is to get more info. regards, tom lane
- [HACKERS] initdb failure Kevin O'Gorman
- Tom Lane