Thanks, this is the case.
As for changing it, docs seem to suggest that encoding can be set only upon
database creation. The database which we need to change is running in
production although with fairly low traffic at the present time. Would the
best suggestion be to dump the current database and re-import? And if so,
any hint on how to indicate the encoding upon creation? Docs probably state
how but just thought I'd ask.
On 3/26/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin McCarthy" <kemccarthy1(at)gmail(dot)com> writes:
> > Often users will copy and paste text directly from MS Word docs into the
> > forms which will invariably contain Microsoft's proprietary formatting
> > characters such as 'smart' quotes, trademark, copyright symbols, accent
> > grave, etc. We've set the HTML pages as UTF-8 and the database
> connection to
> > UTF-8. However when our calls to import the data that includes any of
> > characters into the database, the queries fail complaining that e.g.
> > "[nativecode=ERROR: character 0xe28093 of encoding "UTF8" has no
> > in "LATIN9"]"
> That error suggests that your database encoding is LATIN9, not UTF-8.
> You need to change it. Beware that you need the server's locale
> settings to be in step, too.
> regards, tom lane
In response to
pgsql-novice by date
|Next:||From: David Monarchi||Date: 2007-03-27 04:27:37|
|Subject: postgres 8.2 "end-of-copy marker corrupt"|
|Previous:||From: Sean Davis||Date: 2007-03-26 19:16:38|
|Subject: Re: indexed aggregates?|