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

Re: More Code Page wierdness

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers-win32(at)postgresql(dot)org,Magnus Hagander <mha(at)sollentuna(dot)net>
Subject: Re: More Code Page wierdness
Date: 2005-01-11 04:57:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Is this codepage problem related to people getting the "can't map shared
memory to a fixed address" problem some were having when using "*" for
listen_addresses?  I don't think so but wanted to ask.

Also, is there anyway we can detect this problem when it happens and
throw a clear error?  I don't like adding 'any' as a new value at this


Simon Riggs wrote:
> Spent a few hours today diagnosing some errors on Win32 (on Windows
> Server 2003). These were, I think, wrongly identified as being Windows
> Installer problems, so I believe Magnus was chasing his tail also.
> The problem seemed to be code page related...
> If you set listen_addresses="*" then the pgsql server doesn't recognise
> this because * in one code page is different from * in another. It looks
> like a *, but it isn't...
> Setting listen_addresses to other valid values works just fine....tested
> with "localhost" using local TCP/IP connection; "localhost, 10.0.0.x"
> with access from 10.0.0.x...all working fine.
> Changing the default Language setting to match that of your keyboard is
> only a temporary workaround, since you can't be sure which code page is
> in use by any particular application or window. The only way to be sure
> is to set the default code page to the current locale and reboot, but
> I'm not sure that catches everything either once things have been
> edited.
> ISTM that the code page comments for psql are NOT the only ones that get
> effected by any code page mismatch. (and BTW, Windows 1252 is the UK
> default, not just the German - it is "Latin I"). ***Please put them back
> onto the Windows Installation page, where they should be***
> Anyway, main point here guys is deep code page wierdness is a wider
> problem than was at first thought...
> More testing required....and more on this particular problem to follow.
> I may suggest adding "any" as an option in the listen_addresses GUC, to
> ease the pain of this...but that seems too narrow a solution, much like
> the earlier suggestion to put the code page comments only on psql....
> These are definitely not Windows Installer problems because it is
> perfectly valid action to change the Language of a server, at least in
> Europe. The server should work, no matter what any installer
> did/does....just the same as the server knows not to start if the
> installer incorrectly set up the rights of the instance owning userid.
> -- 
> Best Regards, Simon Riggs
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>       message can get through to the mailing list cleanly

  Bruce Momjian                        |
  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

In response to


pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-01-11 05:35:32
Subject: Re: More Code Page wierdness
Previous:From: Mike G.Date: 2005-01-11 04:11:29
Subject: Re: More Code Page wierdness

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