| > .. and the delta code to be committed upstream is less than 2K LOC. Then mainline it? The last commit that /postgres/postgres and /orioledb/postgres share (1) is 6 months old for 15.2? I mean, this is literally what I'm pointing out in my comment; you're chasing a moving target. Every change postgres makes, you have to merge in check it doesn't conflict, roll out a new patch set... ...and, you're already falling behind on it. So, going forward, how do you plan to keep up to date...? ...because it looks to me, like a < 2K LOC isn't a fix for this problem; it hasn't solved it for you, as time goes forwards, it will continue not to be a solution to the problem; annd... > Currently the changes needed to Postgres core are less than a 1000 lines of code. Due to the separate development schedules for Postgres and OrioleDB, these changes cannot be unstreamed in time for v.15. (2) ^ They were < 1000 lines a year ago, apparently. So the problem is getting worse over time. Seems like the solution is mainlining those changes... not just intending to mainline them. Until then... I really just see this as a postgres fork. [1] - https://github.com/postgres/postgres/commit/78ec02d612a9b690... vs https://github.com/orioledb/postgres/commit/78ec02d612a9b690... [2] - https://github.com/orioledb/postgres/issues/2 |