Re: Bad dumps...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stef <svb(at)ucs(dot)co(dot)za>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Bad dumps...
Date: 2004-07-13 14:24:36
Message-ID: 15686.1089728676@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Stef <svb(at)ucs(dot)co(dot)za> writes:
> I found that it was actually a '\\N' value only that causes
> dumps to dump successfully, but fail on import (When using COPY),
> because both '\N' and '\\N' are seen as null by the COPY statement.

This is demonstrably not so. You might have trouble with data coming
from somewhere else, if the source doesn't understand the quoting rules
for COPY data. But I can dump and restore a table containing '\N' and
variants of that without any trouble.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-07-13 14:29:44 Re: Point in Time Recovery
Previous Message Mitch Pirtle 2004-07-13 14:06:02 Re: [ADMIN] [PHP] Secure DB Systems - How to