Hello, TL> Ivan <[EMAIL PROTECTED]> 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! -- Best regards, Ivan mailto:[EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
