| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org, Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
| Subject: | Re: Best practices for moving UTF8 databases |
| Date: | 2009-07-14 13:52:29 |
| Message-ID: | 20090714135229.GB4799@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andres Freund wrote:
> On Tuesday 14 July 2009 11:36:57 Jasen Betts wrote:
> > if you do an ascii dump and the dump starts out "SET CLIENT ENCODING
> > 'UTF8'" or similar but you still get errors.
> Do you mean that a dump from SQL_ASCII can yield non-utf8 data? right. But
> According to the OP his 8.3 database is UTF8...
> So there should not be invalid data in there.
I haven't followed this thread, but older PG versions had less strict
checks on UTF8 data, which meant that some invalid data could creep in.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clark Slater | 2009-07-14 14:04:12 | filter duplicates by priority |
| Previous Message | Alvaro Herrera | 2009-07-14 13:49:41 | Re: Ascending / Descending Indexes |