Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WAL files
Вложения
В списке pgsql-hackers по дате отправления:
| От | Stephen Frost |
|---|---|
| Тема | Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WAL files |
| Дата | |
| Msg-id | 20180123025648.GE2416@tamriel.snowman.net обсуждение |
| Ответ на | Re:Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WALfiles (chenhj <chjischj@163.com>) |
| Ответы |
Re:Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WALfiles
|
| Список | pgsql-hackers |
Greetings! * chenhj (chjischj@163.com) wrote: > Rebased and removed the whitespace. Thanks for working on this, I agree that it seems like a pretty cool optimization for pg_rewind. I've only read through the thread to try and understand what's going on and the first thing that comes to mind is that you're changing pg_rewind to not remove the WAL from before the divergence (split) point, but I'm not sure why. As noted, that WAL isn't needed for anything (it's from before the split, after all), so why keep it? Is there something in this optimization that depends on the old WAL being there and, if so, what and why? That's also different from how pg_basebackup works, which I don't think is good (seems like pg_rewind should operate in a pretty similar manner to pg_basebackup). Setting this back to Waiting for Author but hopefully you can reply soon and clarify that, possibly adjusting the patch accordingly. Thanks! Stephen
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера