"Mareks Malnacs" <[EMAIL PROTECTED]> writes:
> configure script forbids me to use following options:
> --enable-locale --enable-multibyte=UNICODE --enable-odbc --with-java
> --enable-unicode-conversion
All those options have been obsolete for a long time.
> initdb -E UNICODE -A password -W
> This command says that it will use C encoding instead of specified UNICODE,
You sure you aren't confused about locale vs. encoding? You want to
specify a locale setting too, probably.
regards, tom lane
---------------------------(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
