Pavel, Justin, >> Is there any reason to continue with two separate threads and CF entries ? >> The original reason was to have a smaller patch for considerate late in v15.
> I see the main goal of this split is to make discussion of this (easier) > thread separate to the discussion of a whole patchset which is expected to be > more thorough. +1. This was done per explicit request in the first thread. >> But right now, it just seems to cause every update to imply two email >> messages >> rather than one. >> >> Also, since this patch series is large, and expects a lot of conflicts, it >> seems better to update the cfapp with a "git link" [0] where you can >> maintain a >> rebased branch. It avoids the need to mail new patches to the list several >> times more often than it's being reviewed. Yep, this is a bit inconvenient. Personally I didn't expect that merging patches in this thread would take that long. They are in "Ready for Committer" state for a long time now and there are no known issues with them other than unit tests for SLRU [1] should be merged first. I suggest we use "git link" for the larger patchset in the other thread since I'm not contributing to it right now and all in all that thread is waiting for this one. For this thread we continue using patches since several people contribute to them. [1]: https://commitfest.postgresql.org/38/3608/ -- Best regards, Aleksander Alekseev
