Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim McAuley <mcauleyt(at)tcd(dot)ie>, pgsql-hackers(at)postgreSQL(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date: 2003-09-26 16:00:59
Message-ID: 20030926160059.GC8415@feivel.fam-meskes.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc

On Fri, Sep 26, 2003 at 11:01:34AM -0400, Tom Lane wrote:
> > I am getting the error:
> > "
> > creating information schema... ERROR: end-of-copy marker does not match
> > previous newline style
> > CONTEXT: COPY FROM, line 361
> > "
>
> That's interesting. COPY is complaining because the \. terminator in
> the file it's been fed has a different kind of newline after it than
> the newlines earlier in the file (LF vs CR/LF, no doubt). The part

Well actually I'm not so sure. I tried installing 7.4 from Oliver's
Debian packages and experienced exactly the same. We have yet to find
out why, but I doubt newlines changed between his Debian system and mine.

> of the initdb script that must be causing this is
>
> echo "COPY information_schema.sql_features (feature_id, feature_name, sub_feature_id, sub_feature_name, is_supported, comments) FROM STDIN;"
> cat "$datadir"/sql_features.txt
> echo "\."
> ) \
> | "$PGPATH"/postgres $PGSQL_OPT template1 > /dev/null || exit_nicely
> echo "ok"
>
> so it appears that cygwin's "echo" generates a different newline style
> than what got put into sql_features.txt. A possible way to fix this is
> to put the "\." line into sql_features.txt, but maybe there's a cleaner
> answer. Peter, any thoughts?

Putting the "\." line into sql_features.txt did help me, too.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2003-09-26 16:02:54 Re: Good way to insert/update when you're not sure of
Previous Message Shridhar Daithankar 2003-09-26 15:44:27 Re: Good way to insert/update when you're not sure of duplicates?

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2003-09-26 16:11:28 Re: [ADMIN] postgres 6.2 vacuum
Previous Message Andreas Pflug 2003-09-26 15:50:47 Re: [HACKERS] Threads vs Processes

Browse pgsql-jdbc by date

  From Date Subject
Next Message CRAIG GOLBY 2003-09-26 16:24:27 Tomcat - PostgreSQL - Cannot load JDBC driver class "null"
Previous Message Matthew T. O'Connor 2003-09-26 15:17:25 Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)