Re: Adding pg_dump flag for parallel export to pipes

From: Nitin Motiani <nitinmotiani(at)google(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Hannu Krosing <hannuk(at)google(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adding pg_dump flag for parallel export to pipes
Date: 2025-04-28 08:22:53
Message-ID: CAH5HC94_Miqg9wnu=wFBrDR0q97aE6-VO_A3ObPHTMQ5Xjki2g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for the feedback, Thomas.

> 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?

Yes, we didn't add the failed tests to the patch. We'll add those and
send new patches.

> 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.

Will follow these recommendations when sending the next set of patches.

Regards,
Nitin Motiani
Google

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-04-28 08:40:53 Re: using index to speedup add not null constraints to a table
Previous Message Andrey Borodin 2025-04-28 07:04:05 Re: Call for Posters: PGConf.dev 2025