On 2008-02-07 01:17, Tino Schwarze wrote:
Hi Dean,
On Wed, Feb 06, 2008 at 06:29:02PM -0800, Dean Gibson (DB Administrator) wrote:
2. ... Should I be running INITDB w/ "-locale POSIX -E UTF8", or just "-locale POSIX" (implying "-E SQL_ASCII")? Or does it make a difference, since I always specify the desired database encoding when I "CREATE DATABASE... ENCODING '...';"?
AFAIK, it shouldn't make a difference. -E is just the default encoding for new databases.
Actually, "-E" also affects the encoding of the base PostgreSQL
databases. W/o "-E":
=> \l
List of databases
Name | Owner | Encoding
-----------+----------+-----------
postgres | postgres | SQL_ASCII
template0 | postgres | SQL_ASCII
template1 | postgres | SQL_ASCII
If I INITDB /w "-E UTF8":
=> \l
List of databases
Name | Owner | Encoding
-----------+----------+----------
postgres | postgres | UTF8
template0 | postgres | UTF8
template1 | postgres | UTF8
So, the interesting question is, does the difference in the encoding of
the base databases affect performance or capability in any way?
-- Dean
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
