Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
От | Michael Meskes |
---|---|
Тема | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Дата | |
Msg-id | 20030926160059.GC8415@feivel.fam-meskes.de обсуждение исходный текст |
Ответ на | initdb failure (was Re: [GENERAL] sequence's plpgsql) (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
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@jabber.org Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
В списке pgsql-hackers по дате отправления: