Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)
Дата
Msg-id CAB7nPqQWU80D2JJk8Y6jQ+SRjHDFE1POm7Ck9uu-bO==3ahDPA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)  (Fujii Masao <masao.fujii@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Wed, Jul 1, 2015 at 10:58 AM, Fujii Masao wrote:
> On Tue, Jun 9, 2015 at 10:09 AM, Michael Paquier wrote:
>> That's a valid concern. What about the attached then? I think that it
>> is still good to keep upto to copy only data up to the switch point at
>> recovery exit. InstallXLogFileSegment() changes a bit as well because
>> of its modifications of arguments.
>
> Applied. Thanks!

Thanks for showing up.
-- 
Michael

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)
Следующее
От: Fujii Masao
Дата:
Сообщение: WAL-related tools and .paritial WAL file