Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGRHx-00034B-1q for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Sep 2020 18:27:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kGRHv-00086D-27 for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Sep 2020 18:27:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGRHu-00085v-Q8 for pgsql-hackers@lists.postgresql.org; Thu, 10 Sep 2020 18:27:14 +0000 Received: from mail-lj1-x244.google.com ([2a00:1450:4864:20::244]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kGRHs-00066l-5F for pgsql-hackers@lists.postgresql.org; Thu, 10 Sep 2020 18:27:14 +0000 Received: by mail-lj1-x244.google.com with SMTP id b19so9426538lji.11 for ; Thu, 10 Sep 2020 11:27:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IpF402SL/2fS8jhunumwZ5kuQzXydqc1cFKSav4UxHw=; b=VIljWBtZUDp5+a72WbBuPqm4ltdyoMByPYzDX2bwSb116Mfrfc3uUElTZu6b5hX4FZ /j7Mq0TbkBaas/3xLvqd4txS2Muda6WWzWr3xUR6OIlCvK49kQg/mugKGBtQoPuZNls4 NJ1qhcJ5JOfJMfyoL98Nj5SODaWEdgYiTuoeWnuYk09gDy1OUT7y4FMfLbAnT3WvJGoX cp0bPXGICTLO/v5rzyNFZqAAm90smisVEuAS9AhS2q4eOmIUCgMhpG8/27VhuuSPEeTb WEQZqqiuSUddtbRNhBAz6oKl3RCZWkT/Ay3aJKR8j1mL1t7wuFTKVAvg1FoEgcgJDY4+ cj6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IpF402SL/2fS8jhunumwZ5kuQzXydqc1cFKSav4UxHw=; b=mTpx54TsnhJWrJvc2/R1BoAmUbcEocxIIuGEicYW3qpSKYDSYqj6hsAtqbzuvRqem2 ej1UyyBS9B2BcjIX7Ru84dt0IwOwcE5rw+iNJchqwT8S/NzH/ECAowU+AkXGANwmB2zB eLMkajTr1//SFzdO9gsZTXwwFTzE/dNg3iCjraeuu4h3ff6BgfWQBeW3EOM1c5CHmBbU eNChez4aQGymIVq5IgCm1uZnn1fVAvpV3Djj9sEdD2lN/AUcvjmhL1nmEY9B0o6wzz+b f4HbGjJDXWI1JqgO8WoDvOuxDYKn8muSFzgybO1kyc6THrk3HPDhE0DspOHDBr70tlAK zGFw== X-Gm-Message-State: AOAM530iMO6fNo8P7tgLw+f4NCKvoQUguFoXpr0FkCrzx799ItOKTkZI JHE+bpw3saLgWMsRvLMC9Sgp0hrMIZ1sZOxI/k8= X-Google-Smtp-Source: ABdhPJwASNlrvlTC9GF71e/Jk9zJV6mDfk5u5tXE25CktNPP6I+W9ZEzS8gJW/0pGgxA3Lv45Yxi4InJDPdYQWUW8sU= X-Received: by 2002:a2e:141c:: with SMTP id u28mr5481876ljd.72.1599762431244; Thu, 10 Sep 2020 11:27:11 -0700 (PDT) MIME-Version: 1.0 References: <1850884.1599601164@sss.pgh.pa.us> <148145.1599703626@sss.pgh.pa.us> <251830.1599757015@sss.pgh.pa.us> In-Reply-To: <251830.1599757015@sss.pgh.pa.us> From: Robert Haas Date: Thu, 10 Sep 2020 14:26:59 -0400 Message-ID: Subject: Re: SIGQUIT handling, redux To: Tom Lane Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Sep 10, 2020 at 12:56 PM Tom Lane wrote: > Also, man that CHECK_FOR_INTERRUPTS() looks like trouble. > Could we take that out? Maybe I'm missing something, but why wouldn't that be a horrible idea? We do not want to have long waits where we refuse to respond to interrupts. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company