The rebase was indeed trivial (git handled everything automatically), because my first patch was doing a superset of the changes that were committed in b6dfee28f. Attached are the new patches.
On Tue, 14 Mar 2023 at 19:04, Greg Stark <st...@mit.edu> wrote: > > On Tue, 14 Mar 2023 at 13:59, Tom Lane <t...@sss.pgh.pa.us> wrote: > > > > "Gregory Stark (as CFM)" <stark....@gmail.com> writes: > > > It looks like this needs a big rebase in fea-uth.c fe-auth-scram.c and > > > fe-connect.c. Every hunk is failing which perhaps means the code > > > you're patching has been moved or refactored? > > > > The cfbot is giving up after > > v14-0001-libpq-Run-pgindent-after-a9e9a9f32b3.patch fails, > > but that's been superseded (at least in part) by b6dfee28f. > > Ah, same with Jelte Fennema's patch for load balancing in libpq. > > -- > greg
v15-0003-Return-2-from-pqReadData-on-EOF.patch
Description: Binary data
v15-0002-Refactor-libpq-to-store-addrinfo-in-a-libpq-owne.patch
Description: Binary data
v15-0001-libpq-Run-pgindent-after-a9e9a9f32b3.patch
Description: Binary data
v15-0004-Add-non-blocking-version-of-PQcancel.patch
Description: Binary data
v15-0005-Start-using-new-libpq-cancel-APIs.patch
Description: Binary data
