Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled.
От | Simon Riggs |
---|---|
Тема | Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled. |
Дата | |
Msg-id | CA+U5nMKcuUgmCBuPUXV2zD2C2K+RCC3tQ_QLuJ-vmYQmdWbkMQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [COMMITTERS] pgsql: Reset master xmin when
hot_standby_feedback disabled.
|
Список | pgsql-hackers |
On 15 July 2014 19:15, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Where was the discussion of > why this change should be back-patched? Your question has broader implications. Currently commit messages do not reference the conversations that led to them and a great many use entirely different descriptions on-list and in the commit message, nor are entries added to conversations to reflect commits. I share your pain in not being able to follow or remember what led to many of them. In fact, I'm pretty sure more than a few commits have no public discussion at all, though mostly there is good discussion. I'm happy to follow any agreed process we lay out. -- Simon Riggs http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: