Huang GeHua <[EMAIL PROTECTED]> writes:
> I want create a new database with the GB18030 encoding.But the
> pgAdminIII tell a error "GB18030 is not a valid encoding name".How can
> i do for it?
The docs say that GB18030 is supported as a client-side encoding only.
So pick any superset encoding (UTF8 maybe?) as the database encoding,
and then set client_encoding to GB18030.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
