From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Mage <mage(at)mage(dot)hu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: lower function |
Date: | 2005-04-06 22:37:34 |
Message-ID: | 1112827054.20921.52.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2005-04-06 at 17:26, Mage wrote:
> Tom Lane wrote:
>
> >Mage <mage(at)mage(dot)hu> writes:
> >
> >
> >>It's serious.
> >>
> >>
> >
> >That's a Perl bug not a Postgres bug: libperl should not change the
> >process's locale settings, or at least if it does it should restore
> >the prior settings before returning. It doesn't.
> >
> >
> >
> I checked with show all, client and server encoding remained latin2, and
> lc_ctype remained hu_HU. However, the lower function got corrupted
> (encoding) until the end of the session.
>
> I can reproduce the bug on an Debian Sarge and on a Gentoo. Both are
> up-to-date.
>
> What should I do? Subscribe to perl list and tell about this? I have to
> write a trigger which can't be written well in plpgsql. My options are
> to learn python or tcl on basic level in one day. I am not sure I want
> and can do this.
You're far more likely to learn tcl or python or php in an afternoon
than to get a patched perl executable in that time.
But I'd still report the bug to them.
From | Date | Subject | |
---|---|---|---|
Next Message | Tino Wildenhain | 2005-04-06 22:40:42 | Re: COPY command use UTF-8 encoding and NOT |
Previous Message | David Parker | 2005-04-06 22:37:33 | Re: monitoring database activity on solaris |