| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Show encoding in initdb messages |
| Date: | 2004-06-21 14:29:51 |
| Message-ID: | 40D6F0DF.9010100@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2004-06-21 14:39:41 | Re: Compile failure with SSL |
| Previous Message | Tom Lane | 2004-06-21 13:58:03 | Re: Show encoding in initdb messages |