Martin Gainty wrote:
> character encoding is implemented at Database level not the table
> http://www.postgresql.org/docs/8.2/interactive/sql-createdatabase.html
> CREATE DATABASE name
> [ [ WITH ] [ OWNER [=] dbowner ] [ TEMPLATE [=] template ]
> [ ENCODING [=] encoding ]
> [ TABLESPACE [=] tablespace ]
> [ CONNECTION LIMIT [=] connlimit ] ]
>
> vs Table
> CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name ( [
> { column_name data_type [ DEFAULT default_expr ] [ column_constraint [
> .. ] ]
> | table_constraint
> | LIKE parent_table [ { INCLUDING | EXCLUDING } { DEFAULTS |
> CONSTRAINTS } ] ... }
> [, ... ]
> ] )
> [ INHERITS ( parent_table [, ... ] ) ]
> [ WITH ( storage_parameter [= value] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
> [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
> [ TABLESPACE tablespace ]
>
> HTH
> M-
> ----- Original Message -----
> From: "Tom Hart" <tomhart@coopfed.org>
> To: "Postgres General List" <pgsql-general@postgresql.org>
> Sent: Wednesday, January 23, 2008 3:32 PM
> Subject: [GENERAL] retry: converting ASCII to UTF-8
I think you may have misunderstood. I realize that encoding is a
database setting, which is why I originally dumped and recreated the
whole db. I tried a full restore with some success, but it kept hanging
on a specific table, a very large one. I decided to limit the dump and
restore to that table, though the from database is encoded 'SQL-ASCII'
and the to database is 'UTF8'. I must have explained it poorly. My
current problem is waiting for the third message to finally post to this
list so I can get help with my 'out of memory' error.
Thanks for your help anyway :-)
--
Tom Hart
IT Specialist
Cooperative Federal
723 Westcott St.
Syracuse, NY 13210
(315) 471-1116 ext. 202
(315) 476-0567 (fax)
--
Tom Hart
IT Specialist
Cooperative Federal
723 Westcott St.
Syracuse, NY 13210
(315) 471-1116 ext. 202
(315) 476-0567 (fax)