I see the problem now. It was my file parser that was escaping the value
then passing it to PQescapeString which resulted in \\n instead of \n.
Guess I was on a wild goose chase. I guess PQescapeString() and
PQputline() are mutally exclusive ... my bad!
Thanks,
Marc L.
Tom Lane wrote:
> Marc
Marc Lavergne <[EMAIL PROTECTED]> writes:
> Just to give a little background, using pgdump in "default" mode creates
> a dump file that includes inline newlines and tabs.
How old a PG release are you using? COPY has quoted special characters
properly for a long time.
re
Just to give a little background, using pgdump in "default" mode creates
a dump file that includes inline newlines and tabs. The solution is to
use the -Fc option but it's a little late for that if all one has is a
"default" dump file. I was hoping to simply run a conversion on the file
to cr
