Re: Problem while setting the fpw with SIGHUP

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem while setting the fpw with SIGHUP
Date: 2018-07-28 23:19:11
Message-ID: 20180728231911.GB1471@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 28, 2018 at 07:10:24PM +0530, Amit Kapila wrote:
> I have just responded to your first patch (0001). Can you once again
> summarize what the 0002 exactly accomplishes? I think one of the
> goals is to fix the original problem reported in this thread and other
> is you have found the concurrency issue. Is it possible to have
> separate patches for those or you think they are interrelated and
> needs to be fixed together?

That would be nice. The last time I read this thread I have been rather
confused about what was being discussed, what were the set of problems,
and what was being fixed. Speaking of which, this is one of the bugfix
patches I wanted to look at once I have untanggled the autovacuum one
for temporary relations and the DOS issues with lock lookups.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-07-28 23:59:00 Re: Removing useless \. at the end of copy in pgbench
Previous Message Michael Paquier 2018-07-28 22:59:52 Re: add verbosity to pg_basebackup for sync