Magnus Hagander <magnus@hagander.net> writes:
> I guess one option could be to just remove it, unconditionally. And
> assume that any users who is running it manually read that in docs
> somewhere that tells them what to do next, and that any user who's
> running it under a wrapper will have the wrapper set it up?
I could get behind that, personally. (1) I think most end-users don't
run initdb by hand anymore. (2) The message is barely useful; what
it mostly does is to distract your attention from the slightly
more useful info printed ahead of it.
>> would be, though. Maybe we need to add some kind of text adventure game
>> into initdb.
> I do like this idea though...
+1
regards, tom lane