Re: Adding pg_dump flag for parallel export to pipes - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Adding pg_dump flag for parallel export to pipes
Date
Msg-id CAMT0RQRbO5tkubbX8OiSt9PY8wwKaAfT10FFp6SF4Od3Xhi18Q@mail.gmail.com
Whole thread Raw
In response to Re: Adding pg_dump flag for parallel export to pipes  (Mahendra Singh Thalor <mahi6run@gmail.com>)
List pgsql-hackers
On Sat, Mar 14, 2026 at 10:37 PM Mahendra Singh Thalor
<mahi6run@gmail.com> wrote:
>
Thanks for reviewing this.

> Comment3:
> Please can we rename "--pipe-command" to "--pipe" only.

the original choice was inspired by the COPY command which has

COPY ... TO { 'filename' | PROGRAM 'command' | STDOUT }
COPY ... FROM { 'filename' | PROGRAM 'command' | STDIN }

and the lack of TO or FROM, so PROGRAM 'command' became --pipe-command

Other options could be --to-pipe for pg_dump and --from-pipe for pg_restore.
Or --to-program , --from-program to be closer to COPY syntax,

Or even --pipe-command-pattern to signify that there is some name
replacement done for each invocation

But thinking more about it the option name does indeed not need to be
fully self-documenting :)

So I would be ok to shortening it to just --pipe

---
Regards
Hannu



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Proposal: common explicit lists for installed headers
Next
From: Álvaro Herrera
Date:
Subject: Re: some more include removal from headers