From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | "Patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Show encoding in initdb messages |
Date: | 2004-06-21 14:55:54 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BD0B@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-21 15:12:11 | Re: Show encoding in initdb messages |
Previous Message | Merlin Moncure | 2004-06-21 14:39:41 | Re: Compile failure with SSL |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-21 15:12:11 | Re: Show encoding in initdb messages |
Previous Message | Tom Lane | 2004-06-21 14:44:29 | Re: Show encoding in initdb messages |