| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| 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 14:56:22 |
| Message-ID: | 200907141656.23132.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday 14 July 2009 15:52:29 Alvaro Herrera wrote:
> 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.
But that was from 8.2 -> 8.3 and not 8.3->8.4 I think?
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Mead | 2009-07-14 15:27:45 | Re: pg_dump of a big table |
| Previous Message | Lawrence Wong | 2009-07-14 14:33:19 | Re: cache lookup failed for function 72629 |