Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
От | Bruce Momjian |
---|---|
Тема | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Дата | |
Msg-id | 200309261957.h8QJvHf01519@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) ("scott.marlowe" <scott.marlowe@ihs.com>) |
Ответы |
Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Список | pgsql-hackers |
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 TABLEtest=> insert into test values ('\r');INSERT 17158 1test=> copy test to '/tmp/out';COPY Then 'vi' /tmp/out. It should show \r, not ^M. Please report back. -- 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 по дате отправления: