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

From Magnus Hagander
Subject Re: Show encoding in initdb messages
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34BD0B@algol.sollentuna.se
Whole thread Raw
In response to Show encoding in initdb messages  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Show encoding in initdb messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
> > The reason it will help with support is because newbies will go
> > "SQL_ASCII! I don't want ascii!".
>
> No they won't.  They will likely not even notice this message
> in the sea of other messages they've never seen before; and
> even if they do notice it, they will certainly not realize
> that they don't want it.  If the message were to *say* "this
> is probably a bad choice because it's incompatible with your
> locale selection", then it might possibly have the effect
> you're hoping for, but I don't see how we can find that out.

Another way would be to make -E a mandatory parameter, and remove the
default completely. That way you have to make a conscious decision.
Can't claim surprise then.


//Magnus

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Show encoding in initdb messages
Next
From: Tom Lane
Date:
Subject: Re: Show encoding in initdb messages