Peter Eisentraut wrote: > Tom Lane writes: > > > 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? > > There's no clean answer to this on Cygwin. This specific case is just a > little problem that we could solve locally, but in general you'll just end > up annoying people if you require them to use consistent line endings on > Cygwin.
This error is coming from the new 7.4 COPY code that allows \r\n as a line terminator. Requiring the end-of-line to be consistent seemed to be the only way to be sure we were not eating a literal carriage return in the data stream. Let's put the "\." into sql_features.txt and see if that fixes it, or can we use echo -c "\.\n" in initdb? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
