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

From scott.marlowe
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id Pine.LNX.4.33.0309261409030.1165-100000@css120.ihs.com
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Fri, 26 Sep 2003, Bruce Momjian wrote:

> scott.marlowe wrote:
> > > OK, 'vi' shows it as:
> > >     
> > >     COPY people2 (id, persons) FROM stdin;
> > >     59      Chance Terry--S
> > >     60      ^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?
> > 
> > The originating system is a RedHat 7.2 box with postgresql 7.2.x running 
> > on it.
> > 
> > The destination system is a RedHat 7.2 box with postgresql 7.4 beta3 
> > running on it.
> > 
> > The data likely came out of a (gasp, horrors) windows box.
> 
> OK, try this on your 7.2:
> 
>     test=> create table test(x text);
>     CREATE TABLE
>     test=> insert into test values ('\r');
>     INSERT 17158 1
>     test=> copy test to '/tmp/out';
>     COPY
> 
> Then 'vi' /tmp/out. It should show \r, not ^M.  Please report back.

Figured out iv (-b switch, man pages rock) and it's a ^M




pgsql-hackers by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Next
From: Peter Eisentraut
Date:
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)