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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: locales and encodings on Windows


  • From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
  • To: Magnus Hagander <mha(at)sollentuna(dot)net>
  • Cc: Aleksander Kmetec <aleksander(dot)kmetec(at)intera(dot)si>, pgsql-hackers-win32(at)postgresql(dot)org
  • Subject: Re: locales and encodings on Windows
  • Date: Thu, 11 Nov 2004 10:05:22 -0500 (EST)
  • Message-id: <200411111505(dot)iABF5Me10995(at)candle(dot)pha(dot)pa(dot)us>

Added to open items list:

        o Disallow encodings like UTF8 which which PostgreSQL supports
          but the operating system does not


---------------------------------------------------------------------------

Magnus Hagander wrote:
> > Come on, people. This was the second time I reported this bug 
> > and also the second time nobody responded to my report. :-(
> 
> 'fraid I know very little about this stuff, so I can't really comment on
> the mani issue.. Was hoping someone else would pick it up...
> 
> 
> > If it is indeed not possible to initdb with a utf8 (65001) 
> > locale, then this will cause a flood of bug reports once a 
> > large number of people start using PG on Windows. Can 
> > somebody try and confirm this problem? 
> > Simply try running initdb with a --locale value of 
> > german_germany.65001, spanish_spain.65001, 
> > french_france.65001 or any other locale you think should be 
> > supported by your system. You will need to do this from the 
> > command line, not from the installer. Does initdb accept this 
> > value or does it replace it with your current system locale?
> > 
> > Unless somebody can come up with a solution, my suggestion 
> > for a work-around would be to remove unsupported encodings 
> > from the installer or at least warn users that their database 
> > will not be fully functional if they happen to choose one of 
> > the unsupported encodings.
> 
> Yeah, that sounds like what we'll have to do if nobody can fix this
> completely. Do you know enough to say exactly which locale/encoding
> combinations have to be removed fromt he installer?
> 
> Bruce - we probably need an open item on the backend side of this. If
> not, then we need at least someone to say we can't fix this for 8.0.
> Removing it from the installer is just a workaround...
> 
> 
> > Last October there was a discussion on pgsql-hackers about 
> > writing locale support for PG, so it wouldn't depend on the 
> > system for locale functionality any more. Is anyone still 
> > working on that?
> 
> I have no idea, but I'm certain if someone is this is definitly not
> going to happen for 8.0.
> 
> //Magnus
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group