Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: localization problem (and solution)
- From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: localization problem (and solution)
- Date: Mon, 19 Dec 2005 23:24:42 -0600
- Message-id: <m31x08e3xh(dot)fsf(at)conexa(dot)fciencias(dot)unam(dot)mx>
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes: > (Your proposed fix seems entirely useless ... While there are reasons to argue that's Perl fault, IMO, an environment that reflects the current state of the host program is a good compromise, and behave environment-consistent is also a good compromise for libperl (I think some applications of libperl will get really upset if this compromise is broken by the library.) Regards, Manuel.
- Follow-Ups:
- Re: localization problem (and solution)
- From: Tom Lane
- Re: localization problem (and solution)
- References:
- localization problem (and solution)
- From: Manuel Sugawara
- Re: localization problem (and solution)
- From: Tom Lane
- localization problem (and solution)
- Prev by Date: Re: Lock issue when trying to vacuum db
- Next by Date: Re: [pgadmin-hackers] Client-side password encryption
- Previous by thread: Re: localization problem (and solution)
- Next by thread: Re: localization problem (and solution)
- Indexes: