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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)
Date: 2015-07-01 02:06:51
Message-ID: CAB7nPqQWU80D2JJk8Y6jQ+SRjHDFE1POm7Ck9uu-bO==3ahDPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2015-07-01 03:39:11 WAL-related tools and .paritial WAL file
Previous Message Fujii Masao 2015-07-01 01:58:12 Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)