Re: Apparent Problem With NULL in Restoring pg_dump - Mailing list pgsql-general

From Rich Shepard
Subject Re: Apparent Problem With NULL in Restoring pg_dump
Date
Msg-id alpine.LNX.2.00.1109151307340.14093@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Apparent Problem With NULL in Restoring pg_dump  (Andy Colson <andy@squeakycode.net>)
Responses Re: Apparent Problem With NULL in Restoring pg_dump  (Andy Colson <andy@squeakycode.net>)
List pgsql-general
On Thu, 15 Sep 2011, Andy Colson wrote:

> To restore, you are using:  psql dbname < filename correct?

Andy,

   Same error.

   BTW, what prompted this was my discovery that about 1400 rows with site_id
= GW-22 had a newline appended to that string. Using emac's
search-and-replace I took those off and new that I would probably have
duplicate records when trying to replace the table. But, I did not expect
these errors of extra characters after the last datum or something about
blanks in real columns.

   If there's a better way for me to drop the \n versions and elimiate one of
the resulting duplicates, please teach me how and I'll go that route.

Thanks,

Rich

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: Apparent Problem With NULL in Restoring pg_dump
Next
From: Rich Shepard
Date:
Subject: Re: Apparent Problem With NULL in Restoring pg_dump