On Wed, 1 Feb 2023 at 14:49, Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > > On 2023-Jan-31, vignesh C wrote: > > > On Tue, 3 Jan 2023 at 18:38, vignesh C <vignes...@gmail.com> wrote: > > > > 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 > > > 92957ed98c5c565362ce665266132a7f08f6b0c0 === > > > === applying patch ./new_options_take_two_v03f.patch > > > patching file src/include/access/reloptions.h > > > Hunk #1 FAILED at 1. > > > 1 out of 4 hunks FAILED -- saving rejects to file > > > src/include/access/reloptions.h.rej > > > > There has been no updates on this thread for some time, so this has > > been switched as Returned with Feedback. Feel free to open it in the > > next commitfest if you plan to continue on this. > > Well, no feedback has been given, so I'm not sure this is a great > outcome. In the interest of keeping it alive, I've rebased it. It > turns out that the only conflict is with the 2022 -> 2023 copyright line > update. > > I have not reviewed it.
Since there was no response to rebase the patch, I was not sure if the author was planning to continue. Anyways Nikolay Shaplov plans to work on this soon, So I have added this to the next commitfest at [1]. [1] - https://commitfest.postgresql.org/41/3536/ Regards, Vignesh
