Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id 200309261939.h8QJdFx00524@candle.pha.pa.us
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-hackers
scott.marlowe wrote:
> The attached file produces this problem.  Note it's a blank trailing field 
> that looks to be causing it.  The error for this .sql file is:
> 
> ERROR:  literal carriage return found in data
> HINT:  Use "\r" to represent carriage return.
> CONTEXT:  COPY FROM, line 2
> 
> Note that loading this into pico and saving it back out fixes the problem.
> 
> If I remove the preceding row that doesn't end in a blank field, I get a 
> different error, this one:
> 
> ERROR:  end-of-copy marker does not match previous newline style
> CONTEXT:  COPY FROM, line 2

OK, 'vi' shows it as:COPY people2 (id, persons) FROM stdin;59      Chance Terry--S60      ^M\.

which is _exactly the case the error was supposed to catch.  Now, the
big question is where did this dump come from?  Pg version?  OS platform?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: invalid tid errors in latest 7.3.4 stable.
Next
From: Andrew Sullivan
Date:
Subject: Re: 2-phase commit