TL> Ivan <Ivan-Sun1(at)mail(dot)ru> writes:
>> When I create a function in sql or plpgsql languages,
>> their body text is stored in the database files with
>> 0D 0A line ends (I checked it in a hex editor).
>> If I create plain backup using pg_dump
>> it generates functions with
>> 0D 0D 0A on the end of the body lines,
TL> Good ol' Windows :-(. Try writing the dump file with "pg_dump -f file"
TL> instead of "pg_dump >file" ... does that make it better?
This problem is actual for pg_dumpall because there is no -f file
option for it - output is always written to standard output.
Is it possible to add this option to pg_dumpall too?
Thank you for support!
In response to
pgsql-bugs by date
|Next:||From: jmreymond||Date: 2005-10-31 16:24:29|
|Subject: BUG #2011: warning during link of plperl|
|Previous:||From: Tomas Zerolo||Date: 2005-10-31 04:39:56|
|Subject: Re: importing from 8.0.3 unicode problem|