Hi Kirill, On Thu, Feb 5, 2026 at 11:08 PM Kirill Reshke <[email protected]> wrote: > > Sure > This will in fact resolve many problems, not only CVE > So, how do we organize this? Do we need big excel as in gpdb > cherry-pick process? >
I think both approaches could work well — a shared Google Sheet or a GitHub Project/issue tracker. The key is to keep the progress transparent and make it easy for others to participate and contribute. I want to share more ideas on the minior kernel upgrade for the reference. Between PG 14.4 and 14.20 there are ~1352 commits, so a phased upgrade could be a reasonable approach. For example, upgrading incrementally (14.4 → 14.5 → 14.6, etc. ~100 commits per step) or grouping several minor versions per step could help keep the process more controlled and reduce risk. Curious to hear what others think. BTW, would you be interested in leading this upgrade effort, if you have the bandwidth? Having a coordinator would greatly help drive this forward. Best, Dianjin Wang --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
