![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Perhaps you missed my previous message. pg_dumpall has not -f command line option to specify output file - it always send output to standart output. But there is an issue with it in Windows (I described it earlier) - function's line endings are changed from 0D 0A to 0D 0D 0A. |
#3
| |||
| |||
|
|
Perhaps you missed my previous message. pg_dumpall has not -f command line option to specify output file - it always send output to standart output. But there is an issue with it in Windows (I described it earlier) - function's line endings are changed from 0D 0A to 0D 0D 0A. |
#4
| |||
| |||
|
|
Thursday, November 3, 2005, 3:28:41 PM, you wrote: Perhaps you missed my previous message. pg_dumpall has not -f command line option to specify output file - it always send output to standart output. But there is an issue with it in Windows (I described it earlier) - function's line endings are changed from 0D 0A to 0D 0D 0A. AH> Hmm, what do you need that for? Why don't you directly restore the AH> binary dump to a database by using option -d? I don't need to restore binary dump. I need to make a dump of the whole database cluster to plain sql file (what pg_dumpall does). So I have to redirect pg_dumpall's output to a file pg_dump [options] > cluster_dump.sql |
![]() |
| Thread Tools | |
| Display Modes | |
| |