Date: Fri, 8 Aug 2003 12:11:17 -0700 From: Sean Chittenden <sean@chittenden.org> To: Gerard Samuel <gsam@trini0.org> Cc: girgen@pingpong.net Subject: Re: FreeBSD Port: postgresql7-7.3.3 Message-ID: <20030808191117.GP94710@perrin.int.nxad.com> In-Reply-To: <3F20163B.2000403@trini0.org> References: <3F20163B.2000403@trini0.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Im looking for some clarification. > I just upgraded from postgresql 7.2.3, and I previously had it installed > with Multibyte support. > That option isn't available in the Postgresql 7.3.3 port. > According to the Postgresql docs, Multibyte is set enabled by default. > Cool. > Im trying to have all my databases set to "UNICODE" encoding (like how > it was when I had 7.2.3 running) > So I ran initdb with the -E switch to UNICODE. > su -l pgsql -c initdb -E UNICODE > > But the databases still have the SQL_ASCII encoding on them. > $ psql -l > List of databases > Name | Owner | Encoding > -----------+-------+----------- > template0 | pgsql | SQL_ASCII > template1 | pgsql | SQL_ASCII > (2 rows) > > But according to the docs, there may be some auto conversions from > SQL_ASCII to UNICODE > What I would like to know, is if this is true with the current > Postgresql 7.3.3 port? > So I don't have to worry about trying to get them to UNICODE, as it > seems like it cannot do so.... http://developer.postgresql.org/docs/postgres/charset.html http://developer.postgresql.org/docs/postgres/multibyte.html pgsql-general@postgresql.org list is probably more appropriate, or pgsql-novice@postgresql.org. -sc -- Sean Chittenden
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030808191117.GP94710>