Skip site navigation (1) Skip section navigation (2)

Re: Convert string to UNICODE & migration FROM 7.4 to 9.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philippe Lang <philippe(dot)lang(at)attiksystem(dot)ch>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Convert string to UNICODE & migration FROM 7.4 to 9.1
Date: 2011-11-24 20:25:50
Message-ID: 28552.1322166350@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Philippe Lang <philippe(dot)lang(at)attiksystem(dot)ch> writes:
> I have a function under PG 7.4 that returns an xml structure, with the content encoded in UNICODE.

Basically, the only reason you got away with that in 7.4 is that 7.4 is
so lax about encodings.  In general, in modern releases, all text
strings inside the backend are in the database's specified encoding.
Full stop, no exceptions.  If you think you need something different,
you need to rethink your assumptions.

I'd try just dropping the convert() step and see what happens.

			regards, tom lane

In response to

pgsql-general by date

Next:From: Andrus MoorDate: 2011-11-24 20:40:42
Subject: Re: How to get normalized data from tekst column
Previous:From: Gaƫtan AllartDate: 2011-11-24 19:38:39
Subject: Re: General performance/load issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group