Re: Adding pg_dump flag for parallel export to pipes

On Fri, Jun 12, 2026 at 10:50 AM solai v <solai(dot)cdac(at)gmail(dot)com> wrote:
>

> without creating an intermediate dump directory.
> I verified error handling (--pipe='invalid_cmd') as well and correctly
> reported the error as "pg_dump: error: pipe command failed:
> "invalid_cmd": command not found".
> Similarly, --pipe='gzip | false' correctly propagated the child
> process failure. I also performed an end-to-end validation of the new
> functionality by restoring the generated archive using pg_restore
> --pipe. The restore completed successfully, and row counts for the
> test tables matched the original database confirming that dump
> generation, compression, restore, and data integrity all worked
> correctly. One particularly useful improvement I noticed is the
> handling of parallel jobs when the %f placeholder is omitted,
> producing the warning: "pg_dump: warning: parallel jobs with --pipe
> usually require the "%f" placeholder to avoid data corruption from
> multiple workers writing to the same file". This is an usability
> improvement, as it explicitly warns users against a common misuse that
> could otherwise lead to corrupted output when multiple workers write
> to the same destination file. Overall, the patch series worked well
> and the new --pipe support behaves correctly in my testing, also the
> newly added warning for missing %f significantly improves the user
> experience for parallel jobs. The patch looks good to me.
>
>

Thanks for the feedback. Rebasing and uploading v18.