On Thu, 15 Sep 2011, Adrian Klaver wrote:
In your editing of the file did you happen to edit out the \. that is at
the end of the COPY data?
Adrian,
Ah, shoot! I did ... based on an earlier message.
That was the problem.
Many thanks, once again,
Rich
--
Sent via pgsql-general mailing
On Thursday, September 15, 2011 6:24:42 am Rich Shepard wrote:
> On Thu, 15 Sep 2011, Alban Hertroys wrote:
>
>Each row terminates with a \n; when the cursor is at the row end and I
> press ctrl-f (move one character forward), the cursor is at the beginning
> of the next line.
>
>I'm con
On Thu, 15 Sep 2011, Alban Hertroys wrote:
The text in the error is a tab character, so maybe you have an extra tab
somewhere?
Alban,
The column separators are tabs. I've checked a few rows above and below
the cited one and find only a single tab between columns.
If not, perhaps the error
On 15 Sep 2011, at 3:42, Rich Shepard wrote:
> Line 47475 is below the last line with content in the file. Line 47363
> contains:
>
> 96-A000890SC 1996-04-23 Conductance, Specific 394
> uS/cm t \N \N \N
>
> (which is wrapped here, but not in the emacs buffer). Th
Now that I fixed the rows that had the inadvertent newlines in one column,
I'm trying to read in the fixed table from the .sql file produced by
pg_dump. I know there are duplicate rows now that I removed the newlines,
and those are easily fixed (although the reported line numbers don't match
wha
