Re: [HACKERS] WAL logging problem in 9.4.3?

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: noah(at)leadboat(dot)com
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, michael(at)paquier(dot)xyz, 9erthalion6(at)gmail(dot)com, andrew(dot)dunstan(at)2ndquadrant(dot)com, hlinnaka(at)iki(dot)fi, andres(at)anarazel(dot)de
Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
Date: 2020-04-06 00:46:31
Message-ID: 20200406.094631.402837389573618941.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Sat, 4 Apr 2020 15:32:12 -0700, Noah Misch <noah(at)leadboat(dot)com> wrote in
> On Sat, Apr 04, 2020 at 06:24:34PM -0400, Tom Lane wrote:
> > Shouldn't the CF entry get closed?
>
> Once the buildfarm is clean for a day, sure. The buildfarm has already
> revealed a missing perl2host call.

Thank you for (re-) committing this and the following fix. I hope this
doesn't bring in another failure.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-04-06 01:54:09 Re: Reinitialize stack base after fork (for the benefit of rr)?
Previous Message Peter Geoghegan 2020-04-06 00:15:07 Re: nbtree: assertion failure in _bt_killitems() for posting tuple