Please add the unicode use flag to postgresql and use it to toggle --enable-multibyte which turns on support for storing unicode in the database.
Both multibyte and locale support are now always enabled from release 7.3.
If that were the case I would not have filed a bug about it. If I emerge postgresql on my machine, multibyte support is turned off. If I edit the ebuild to specify --enable-multibyte then it works. Is --enable-multibyte turned on by nls? Because if thats what you mean then please add the unicode flag as well. I don't want to have error messages in multiple languages via gettext, I want the database to be capable of storing multibyte characters. There is a global useflag for unicode support which would be a good choice to turn this specific thing on. Please be careful when marking bugs as invalid.
hi tigger I've talked with matsuu about this issue. He says --enable-multibyte flag doesn't anything anymore and HISTORY file in postgresql's tarball says; * Always enable multibyte in compile, remove --enable-multibyte option (Tatsuo) And I've checked source codes(7.4.6) and it seems --enable-multibyte doesn't do anything. We'd like to know what is your real problem. Could you post result of 'emerge -pv postgresql' and 'emerge info'?
Sure: [ebuild R ] dev-db/postgresql-7.4.6 -debug -doc -java -libg++ -nls +pam +perl -pg-hier -pg-intdatetime -pg-vacuumdelay +python +readline +ssl -tcltk -threads +zlib rob@tan rob $ sudo emerge info Portage 2.0.51-r3 (hardened/x86, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.7-hardened-r4 i686) ================================================================= System uname: 2.6.7-hardened-r4 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://foo/gentoo-distfiles" MAKEOPTS="-j2" PKGDIR="/usr/portage//packages/x86/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" PORTDIR_OVERLAY="/usr/portage/linx-overlay" SYNC="rsync://foo/gentoo-portage" USE="x86 apache2 berkdb crypt gd hardened jpeg mmx pam perl pic pie png readline sse ssl zlib"
I read the history file you mentioned and I cannot fathom what it was that magically made unicode work. It obviously wasn't that flag as it doesn't seem to exist anymore. And yet, it was broken, and now it works, after adding a flag which doesn't exist... I'll try unmerging + remerging to see if I can see whats going on.
I'm just gonna kill this and assume user error :)