Re: Adding pg_dump flag for parallel export to pipes

From: Hannu Krosing <hannuk(at)google(dot)com>
To: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Cc: Nitin Motiani <nitinmotiani(at)google(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adding pg_dump flag for parallel export to pipes
Date: 2026-03-15 09:01:35
Message-ID: CAMT0RQRbO5tkubbX8OiSt9PY8wwKaAfT10FFp6SF4Od3Xhi18Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 14, 2026 at 10:37 PM Mahendra Singh Thalor
<mahi6run(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-03-15 09:12:33 Re: some more include removal from headers
Previous Message Zsolt Parragi 2026-03-15 07:40:38 Re: Proposal: common explicit lists for installed headers