"Ron Mayer" <ron@intervideo.com> writes:
>> As for the unescaped CR, it's there sure enough, but this won't tell
>> us where it came from. Could you double-check the version of the server
>> you were dumping from?
> Yup. It was a
> "Postgresql 7.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
> 20020903 (Red Hat Linux 8.0 3.2-7)"
> and "\r" escaping didn't start til 7.2.1.
Doh ... right ...
> Is the best way for me to get 7.2 data to 7.4devel to:
> (1) upgrade 7.2 to 7.2.4 (no dump/restore needed?)
> (2) dump from 7.2.4, and
> (3) restore that dump
Yeah, probably so. The server update is needed to get the \r escaping
correct (unless you want to fix it with sed or some such in the dump
file), and is a good idea anyway considering the known nasty bugs in
7.2.
You could dump with a 7.3 pg_dump instead of 7.2.4, which might provide
better transportability. Right at the moment you cannot use the CVS-tip
pg_dump because CVS-tip libpq won't talk to pre-7.4 servers. (Obviously
that's gonna have to be fixed before release, but it's not on my
critical path right now.)
regards, tom lane
