Re: Hot Standby, release candidate?
От | Tom Lane |
---|---|
Тема | Re: Hot Standby, release candidate? |
Дата | |
Msg-id | 29462.1260804206@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Hot Standby, release candidate? (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Hot Standby, release candidate?
Re: Hot Standby, release candidate? |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Dec 14, 2009 at 6:35 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> Why is (1) important, and if it is important, why is it being mentioned >> only now? Are we saying that all previous reviewers of my work (and >> others') removed these without ever mentioning they had done so? > pgident will remove such white spaces and create merge conflicts for > everyone working on those areas of the code. What I try really hard to remove from committed patches is spurious whitespace changes to pre-existing code. Whether new code blocks exactly match pgindent's rules is less of a concern, but changing code you don't have to in a way that pgindent will undo later anyway is just useless creation of potential conflicts. The whole thing would be a lot easier if someone would put together an easily-installable version of pgindent. Bruce has posted the patches he uses but I don't know what version of indent they're against... regards, tom lane
В списке pgsql-hackers по дате отправления: