Re: Parallel pg_dump's error reporting doesn't work worth squat

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Parallel pg_dump's error reporting doesn't work worth squat
Date: 2016-05-27 08:38:26
Message-ID: 20160527.173826.95124844.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 26 May 2016 10:53:47 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in <5237(dot)1464274427(at)sss(dot)pgh(dot)pa(dot)us>
> Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> >> Next, I got the following behavior for the following command,
> >> then freeze. Maybe stopping at the same point with the next
> >> paragraph but I'm not sure. The same thing occurs this patch on
> >> top of the current master but doesn't on Linux.
>
> > [ need to close command sockets in ShutdownWorkersHard ]
>
> Hah. I had made that same change in the cosmetic-cleanups patch I was
> working on ... but I assumed it wasn't a live bug or we'd have heard
> about it.
>
> Pushed along with the comment improvements I'd made to that function.

Thank you!

regards,

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2016-05-27 08:38:50 Re: Fix a failure of pg_dump with !HAVE_LIBZ
Previous Message Kyotaro HORIGUCHI 2016-05-27 08:38:05 Re: Parallel pg_dump's error reporting doesn't work worth squat