Re: [PATCH] pgbench: add multiconnect option - Mailing list pgsql-hackers

From vignesh C
Subject Re: [PATCH] pgbench: add multiconnect option
Date
Msg-id CALDaNm1XAvr1FOST+uMt6PWoOnqppNv5BEJYQY0p1VxxbpJ4Og@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pgbench: add multiconnect option  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On Wed, 11 Jan 2023 at 22:17, vignesh C <vignesh21@gmail.com> wrote:
>
> On Tue, 8 Nov 2022 at 02:16, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> >
> >
> > Hello Ian,
> >
> > > cfbot reports the patch no longer applies.  As CommitFest 2022-11 is
> > > currently underway, this would be an excellent time to update the patch.
> >
> > Attached a v5 which is just a rebase.
>
> The patch does not apply on top of HEAD as in [1], please post a rebased patch:
> === Applying patches on top of PostgreSQL commit ID
> 3c6fc58209f24b959ee18f5d19ef96403d08f15c ===
> === applying patch ./pgbench-multi-connect-conninfo-5.patch
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file doc/src/sgml/ref/pgbench.sgml
> Hunk #3 FAILED at 921.
> 1 out of 3 hunks FAILED -- saving rejects to file
> doc/src/sgml/ref/pgbench.sgml.rej

There has been no updates on this thread for some time, so this has
been switched as Returned with Feedback. Feel free to change it open
in the next commitfest if you plan to continue on this.

Regards,
Vignesh



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: pg_upgrade test failure
Next
From: vignesh C
Date:
Subject: Re: [PATCH] Completed unaccent dictionary with many missing characters