| From: | Meera Nair <mnair(at)commvault(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Joel Howard <joelhoward(at)commvault(dot)com> |
| Subject: | Query related to pg_dump write to a pipe on a windows client and with compressed format |
| Date: | 2023-12-01 02:57:34 |
| Message-ID: | SJ1PR19MB6162A2DD8656F0E0C6A544A9BA81A@SJ1PR19MB6162.namprd19.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
We tried pg_dump write to a pipe with compressed format and faced issue as in thread referred here.
It was on windows client and for postgres 9.2 version. So during pg_restore, seek error was seen.
With pg_dump writing the dump to a file and then move to another machine for backup, this problem was not there.
But now the issue is that we need to have a lot of free space to write the dump file.
If we use tar format, temporary files created in C:\ take space.
If we use parallel dump format, then also staging the dump output is must.
So trying to understand if the compressed format still needs the staging of output file with the latest versions? Or we can write the output to a pipe to move the data to another machine for backup.
Regards,
Meera
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2023-12-01 04:43:39 | Re: Two started cluster on the same data directory and port |
| Previous Message | Jeff Gerbracht | 2023-12-01 02:08:52 | Feature request for INITCAP() function |