From: | girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | PostgreSQL Dump based backup using pipe |
Date: | 2015-05-27 11:19:37 |
Message-ID: | CAKKd066yz3GeEg9D_8KDPGz38YX=rzFAcGd5paUWaOtOqkNsPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi
We were using named pipe to read dump data from 'pg_dump -Fc' (compressed
format) on Windows.
Restore was failing with 'corrupt dump data' error.
Later found that pg_dump was performing 'illegal seek' on pipe to write the
data, which was causing corrupt dump.
I've two questions.
1. With tar format ( -Ft ) I see that data is written in serial fashion so
we are planning to switched to this format.
Is it safe to use name pipe to read from 'pg_dump -Ft' (tar format) ?
2. On Linux also from strace output of 'pg_dump -Fc' (compressed dump) used
with fifo file, I see 'illegal seek' performed on fifo file too.
But restore doesn't have any issues. Is it safe to use 'pg_dump -Fc' with
output file as fifo on Linux ?
Thanks
Girish
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Lentfer | 2015-05-27 11:32:37 | Re: PostgreSQL Dump based backup using pipe |
Previous Message | Albe Laurenz | 2015-05-27 09:15:40 | Re: monitoring TPS and IOPS |