Re: Show encoding in initdb messages - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject Re: Show encoding in initdb messages
Date
Msg-id 40D6F0DF.9010100@familyhealth.com.au
Whole thread Raw
In response to Re: Show encoding in initdb messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Show encoding in initdb messages
List pgsql-patches
>This should save a lot of support requests, hopefully.
>
>
> I kinda doubt it will save any :-(.  In what situation would this not
> merely be echoing back what the guy had just specifically typed on the
> command line?

When no -E argument is supplied at all, or when they type ISO-8859-1
instead of LATIN1.

The reason it will help with support is because newbies will go
"SQL_ASCII! I don't want ascii!".  Then they will kill initdb, check the
man page and then re-run it with a real encoding.

Seriously NO new postgres user checks the initdb man page before running
is the first time.  I know this from the irc channel...

Either way, I see no reason _not_ to just do it...

Chris


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Show encoding in initdb messages
Next
From: "Merlin Moncure"
Date:
Subject: Re: [HACKERS] Compile failure with SSL