Re: Show encoding in initdb messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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 13:58:03
Message-ID: 1687.1087826283@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> The database cluster will be initialized with locale C.
> The database cluster will be initialized with default encoding UNICODE.

> 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?

If we knew how to detect that the encoding doesn't work with the
selected locale value, then we could get somewhere ...

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-06-21 14:29:51 Re: Show encoding in initdb messages
Previous Message Christopher Kings-Lynne 2004-06-21 07:53:20 Better initdb change