Re: Rework the way multixact truncations work
От | Peter Geoghegan |
---|---|
Тема | Re: Rework the way multixact truncations work |
Дата | |
Msg-id | CAM3SWZR05S9b19xi=q9RfLaa=2-21em8PAAuo+TL8x9SJJFqgQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Rework the way multixact truncations work (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: Rework the way multixact truncations work
|
Список | pgsql-hackers |
On Sun, Nov 8, 2015 at 11:52 AM, Noah Misch <noah@leadboat.com> wrote: >> I'm not following along right now - in order to make cleanups the plan is to revert a couple commits and then redo themprettyfied? > > Yes, essentially. Given the volume of updates, this seemed neater than > framing those updates as in-tree incremental development. I think that's an odd way of representing this work. I tend to remember roughly when major things were committed even years later. An outright revert should represent a total back out of the original commit IMV. Otherwise, a git blame can be quite misleading. I can imagine questioning my recollection, even when it is accurate, if only because I don't expect this. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: