Re: initdb failure in CVS - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: initdb failure in CVS
Date
Msg-id 1794.24.211.141.25.1083850521.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: initdb failure in CVS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: initdb failure in CVS
List pgsql-hackers
Tom Lane said:
> Andrew Dunstan <andrew@dunslane.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




pgsql-hackers by date:

Previous
From: Vinay Jain
Date:
Subject: Re: Is there any method to keep table in memory at startup
Next
From: Shachar Shemesh
Date:
Subject: Re: Multiple "selects" returned from a single stored procedure