This entry has been waiting on author input for a while (our current
threshold is roughly two weeks), so I've marked it Returned with
Feedback.
Once you think the patchset is ready for review again, you (or any
interested party) can resurrect the patch entry by visiting
On Sun, Mar 27, 2022 at 11:07:27AM -0500, Jaime Casanova wrote:
> > > It lacks documentation and I need help with WIN32 part of it, I created
> > > this new mail to put the patch on the next commitfest.
> >
> > The patch currently fails on cfbot due to warnings, likely related due to
> > the
> >
On Mon, Mar 21, 2022 at 05:34:31PM -0700, Andres Freund wrote:
> Hi,
>
> On 2022-02-01 21:57:00 -0500, Jaime Casanova wrote:
> > This patch adds a new option (-J num, --jobs-per-disk=num) in
> > pg_upgrade to speed up copy mode. This generates upto ${num}
> > processes per tablespace to copy
Hi,
On 2022-02-01 21:57:00 -0500, Jaime Casanova wrote:
> This patch adds a new option (-J num, --jobs-per-disk=num) in
> pg_upgrade to speed up copy mode. This generates upto ${num}
> processes per tablespace to copy segments of the same relfilenode
> in parallel.
>
> This can help when you
Hi,
This patch adds a new option (-J num, --jobs-per-disk=num) in
pg_upgrade to speed up copy mode. This generates upto ${num}
processes per tablespace to copy segments of the same relfilenode
in parallel.
This can help when you have many multi gigabyte tables (each segment
is 1GB by
