Re: Additional options for Sync Replication
От | Dimitri Fontaine |
---|---|
Тема | Re: Additional options for Sync Replication |
Дата | |
Msg-id | m2k4fi9e4j.fsf@2ndQuadrant.fr обсуждение исходный текст |
Ответ на | Re: Additional options for Sync Replication (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Additional options for Sync Replication
Re: Additional options for Sync Replication |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > If we accept this patch now because a bunch of > people say they really, really want it, isn't that unfair to the > people to whom we've already said "sorry, the deadline has passed"? No, because each time we're talking procedures we're forgetting about a simple fact. Commiters have the direct responsibility of the code, that is why pushing work from non-commiters takes so much time. Commiting your own code, you don't have a steep learning curve, and you don't have to understand the use case and get convinced. So the rules are not the same for commiter patches and contributor patches, and there's no good in trying to have them the same or pretending they are. In particular, only commiters are able to finish and polish the work between the last commit fest and beta, and then they will be on the hook to get to release candidate and release. But you know all that better than I do. I don't want a release as soon as possible, I want the best we are able to provide, and I think adding in current $subject patch helps reaching this goal. <include "baring show stoppers" QA disclaimer> Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
В списке pgsql-hackers по дате отправления: