> SEPostgres seems qualitatively different to me, though. I think PG > people have avoided reviewing it because (a) they weren't interested in > it and (b) they knew they were unqualified to review it.
I think that you are off-base here. As I've pointed out previously, nobody was ever ASSIGNED to review SE-PostgreSQL. http://archives.postgresql.org/message-id/603c8f070901111132m2a595ec0g677762c1fff58...@mail.gmail.com The reviewing that happened during this CommitFest did not happen on the basis of who was interested in which patches. There was a bit of that, but for the most part people reviewed the patches that they were asked to review. I assumed (am I the only one?) that the REASON why we were not asked to review SE-PostgreSQL or Hot Standby is because the committers were planning to do that themselves due to the complexity of the patches. Now, apparently, that assumption was totally wrong. But this doesn't seem complicated to me. If we bump SE-PostgreSQL to the next CommitFest and assign reviewers, they will review it. Maybe their review will not be 100% perfect, but that is why we have committers. If we continue to NOT assign reviewers, reviewers are unlikely to crawl out of the woodwork, just as they (mostly) didn't crawl out of the woodwork for any other patches (HS/SR being a notable exception). ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers