Re: Interval for launching the table sync worker

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: petr(dot)jelinek(at)2ndquadrant(dot)com
Cc: sawada(dot)mshk(at)gmail(dot)com, peter(dot)eisentraut(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Interval for launching the table sync worker
Date: 2017-04-14 06:09:35
Message-ID: 20170414.150935.60719906.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 13 Apr 2017 20:02:33 +0200, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> wrote in <a06d19af-a63a-c546-873c-818b26f4ef10(at)2ndquadrant(dot)com>
> >> Although this is not a problem of this patch, this is a problem
> >> generally.
>
> Huh? We explicitly switch to CacheMemoryContext before pallocing
> anything that should survive long term.

Ah.. yes, sorry for the noise.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pierre Ducroquet 2017-04-14 06:32:54 Re: Small patch for pg_basebackup argument parsing
Previous Message Michael Paquier 2017-04-14 06:00:55 Re: Rewriting the test of pg_upgrade as a TAP test