Hi, On Tue, 9 Jun 2026 at 00:44, Ayush Tiwari <[email protected]> wrote:
> Hi, > > On Sat, 6 Jun 2026 at 03:35, Daniel Gustafsson <[email protected]> wrote: > >> > On 5 Jun 2026, at 23:05, Nathan Bossart <[email protected]> >> wrote: >> > >> > On Sat, Jun 06, 2026 at 12:57:56AM +0530, Ayush Tiwari wrote: >> >> Thoughts? Does this look like the right approach, or is there a >> >> reason to keep refint around? >> > >> > +1. Do we need an appendix-obsolete entry for the docs? >> >> Seems like a reasonable thing to add. Once merged, we should probably >> add (and >> backpatch) a mention to the docs that the functionality will be removed >> in v20. >> > > v2 attached. 0001 now adds an appendix-obsolete entry under the same > contrib-spi-refint id, so existing /current/ documentation links keep > resolving (mirrors the auth-radius pattern). 0002 is unchanged. > > The back-patched "will be removed in v20" notice on v19 (and older) > I can send it post this merge, as suggested. > > Please let me know if I've missed something more. Or if I should > split v2-0001 into 2 parts, one for removal and the other for appendix- > obsolete entry. > Rebasing. Regards, Ayush
v3-0002-Handle-refint-removal-in-cross-version-pg_upgrade-te.patch
Description: Binary data
v3-0001-Remove-the-refint-contrib-module.patch
Description: Binary data
