Re: NLS for extension - Mailing list pgsql-hackers

From Robert Haas
Subject Re: NLS for extension
Date
Msg-id CA+Tgmob86ZxMmMzDD5yro5nTQOCKoBQ1PN40r408GoRLO1JMag@mail.gmail.com
Whole thread Raw
In response to NLS for extension  (Ed Behn <ed@behn.us>)
Responses Re: NLS for extension
List pgsql-hackers
On Thu, Mar 21, 2024 at 7:49 AM Ed Behn <ed@behn.us> wrote:
>     I'll start by admitting that I am a typical American who only speaks one language.
>     I maintain the PL./Haskell extension (https://github.com/ed-o-saurus/PLHaskell). I recently received a bug report
froma user who is unable to load the extension when they have set lc_messages to something other than 'C' or
'en_US.utf8'(https://github.com/ed-o-saurus/PLHaskell/issues/9). I'm not sure how to address this issue. I know it has
somethingto do with NLS, but I'm confused about what I need to do to get an extension to work. The documentation in
chapter57 of the user's manual seems to address stand-alone programs. At least that is my understanding. 
>     I am using my own makefile, not the one from pg_config.

That seems really weird. You wouldn't think that an NLS problem could
cause an invalid ELF header.

If I were trying to troubleshoot this, I'd set up the failing scenario
(i.e. lc_messages=pt_BR.utf8), set a breakpoint in the server on
errstart, and then perform the failing action. Then I'd use gdb to get
a backtrace from the point where the error was thrown, and hope that
the contents of that backtrace made it more clear what was actually
happening.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Danil Anisimow
Date:
Subject: Re: Comments on Custom RMGRs
Next
From: Sriram RK
Date:
Subject: AIX support