Skip site navigation (1) Skip section navigation (2)

Re: Show encoding in initdb messages

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>,"Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Show encoding in initdb messages
Date: 2004-06-21 15:46:56
Message-ID: 200406211746.56414.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> What I personally wish we could do is eliminate database encoding as
> a separate setting altogether, and drive it off the locale selection.
> I don't know how to do that though.

The information is available:

$ LANG=de_DE locale charmap
ISO-8859-1
$ LANG=de_DE(at)euro locale charmap
ISO-8859-15
$ LANG=de_DE.utf8 locale charmap
UTF-8

But the answer space is infinite:

$ LANG=C locale charmap
ANSI_X3.4-1968

I suspect Japanese users will also have a problem with this mechanism, 
but at least we could keep -E to override the automatic selection.


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-06-21 16:03:38
Subject: Re: Show encoding in initdb messages
Previous:From: Tom LaneDate: 2004-06-21 15:12:11
Subject: Re: Show encoding in initdb messages

pgsql-patches by date

Next:From: Tom LaneDate: 2004-06-21 16:03:38
Subject: Re: Show encoding in initdb messages
Previous:From: Tom LaneDate: 2004-06-21 15:12:11
Subject: Re: Show encoding in initdb messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group