MIME-Version: 1.0
References: <CAH5HC97p4kkpikar+swuC0Lx4YTVkE30sTsFX94tyzih7Cc_=w@mail.gmail.com>
 <CAMT0RQRPJUVsZbv6B=G6ccoZ+OM2vPOG85B6xDd+vKR6-0wt0g@mail.gmail.com>
In-Reply-To: <CAMT0RQRPJUVsZbv6B=G6ccoZ+OM2vPOG85B6xDd+vKR6-0wt0g@mail.gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
Date: Sat, 26 Apr 2025 13:07:09 +1200
Message-ID: <CA+hUKGLL5o6hc4ZPvy=JMuFSKksQiqo0PfSsT5Kr2e30Pag8Hw@mail.gmail.com>
Subject: Re: Adding pg_dump flag for parallel export to pipes
To: Hannu Krosing <hannuk@google.com>
Cc: pgsql-hackers@postgresql.org, Nitin Motiani <nitinmotiani@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BhUKGLL5o6hc4ZPvy%3DJMuFSKksQiqo0PfSsT5Kr2e30Pag8Hw%40mail.gmail.com>
Precedence: bulk

On Tue, Apr 8, 2025 at 7:48=E2=80=AFAM Hannu Krosing <hannuk@google.com> wr=
ote:
> Just to bring this out separately : Does anybody have any idea why pipe c=
ommands close inside tests ?
>
> Re: 003-pg_dump_basic_tests has a few basic validation tests for
> correctmflag combinations. We need to write more automated tests in
> 002_pg_dump.pl but have been running into some issues with environment
> setup due to which certain pipe commands result in the shell process
> becoming defunct. These same commands are working fine in manual
> testing. We are still looking into this.

No comment on the wider project except that it looks generally useful,
and I can see that it's not possible to use the conventional POSIX
filename "-" to represent stdout, because you need to write to
multiple files so you need to come up with *something* along the lines
you're proposing here.  But I was interested in seeing if I could help
with that technical problem you mentioned above, and I don't see that
happening with the current patches.  Do I understand correctly that
the problem you encountered is in some other tests that you haven't
attached yet?  Could you post what you have so that others can see the
problem and perhaps have a chance of helping?  I also recommend using
git format-patch when you post patches so that you have a place to
write a commit message including a note about which bits are WIP and
known not to work correctly yet.