On 3/1/2016 6:04 PM, Premsun Choltanwanich wrote:
> Following your instruction by only modify some parameters to match
> with my system, below is a command I just running under "C:\Program
> Files\PostgreSQL\9.5\bin" on my PostgreSQL 9.5.1 after trying
> that "psql -h 192.168.200.75 clubprogram clubadmin" is worked fine.
>
> My Command:
> pg_dump -Ft -v -b -h 192.168.200.75 -U clubadmin -d clubprogram |
> pg_restore -U clubadmin -d clubprogram
>
> Almost Last Result Message:
> pg_dump: reading rewrite rules
> pg_dump: reading policies
> pg_dump: reading large objects
> pg_dump: reading dependency data
> pg_dump: saving encoding = UTF8
> pg_dump: saving standard_conforming_strings = off
> pg_dump: saving database definition
> pg_restore: [tar archiver] corrupt tar header found in TION (expected
> 0, computed 37579) file position 512
> pg_dump: [tar archiver] could not write to output file: Broken pipe
>
> LOG Message:
> No log is created after running above command.
>
>
> Do you have any other suggestion? Or, May I need to modify some
> parameters on my command?
>
>
>
>
> NOTE: My PostgreSQL 9.5.1 is running on Windows 8 (64bit) and
> PostgreSQL 8.0.13 is running on Windows XP (32bit).
try the dump without the -Ft flag (tar format) and piped into psql...
like...
c:
cd \Program Files\PostgreSQL\9.5\bin
pg_dump -h 192.168.200.75 -U clubadmin -d clubprogram | psql -U
clubadmin -d clubprogram
(after first dropping and recreating the new database)
--
john r pierce, recycling bits in santa cruz