Re: Path case sensitivity on windows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Path case sensitivity on windows
Date: 2009-04-02 15:29:45
Message-ID: 24589.1238686185@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> And this only shows up when the binary is found in the PATH and not
> through a fully specified directory. This is, AFAICT, the only case
> where they can differ. This is the reason why we haven't had any reports
> of this before - nobody using the installer, or doing even a "normal
> style" install would ever end up in this situation.

Hmm. Well, if we use pg_tolower then it will only do the right thing
for ASCII letters, but it seems like non-ASCII in the path leading to
the postgres binaries would be pretty dang unusual. (And I am not
convinced tolower() would get it right either --- it certainly won't
if the encoding is multibyte.)

On balance I'd suggest just using pg_tolower and figuring it's close
enough.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-02 15:38:20 Re: A trivial doc patch for pgstattuple
Previous Message Bruce Momjian 2009-04-02 15:21:06 Re: psql \d* and system objects