From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb failure in CVS |
Date: | 2004-05-06 13:35:21 |
Message-ID: | 1794.24.211.141.25.1083850521.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane said:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Did we actually find a current system where it broke with a straight
>> putenv("LC_ALL")?
>
> Well, the Single Unix Spec does not say that that works, and neither
> does the HPUX man page for putenv, so you're going to have a hard time
> convincing me that it's a portable solution.
Yeah, you're right. In fact SUS seems to be quite brain-dead on this - I
can't see that it says anything about how to unset an enviroment value.
How strange.
> I think the real story is
> simply that no one has tested the C version of initdb hard enough to
> notice whether that line actually accomplished anything or not.
>
I tested on the platforms that were available to me.
OTOH, I wonder if maybe what we previously did w.r.t. TZ didn't work, but
the timezone libs were smart enough to disregard an empty TZ value.
Anyway, you seem to have found a portable solution, so all's well that
ends well.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Shachar Shemesh | 2004-05-06 13:36:40 | Re: Multiple "selects" returned from a single stored procedure |
Previous Message | Vinay Jain | 2004-05-06 13:33:06 | Re: Is there any method to keep table in memory at startup |