Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdNYG-005IQj-W5 for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Feb 2024 04:52:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rdNYF-00G02C-HX for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Feb 2024 04:52:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdNYF-00G022-88 for pgsql-hackers@lists.postgresql.org; Fri, 23 Feb 2024 04:52:47 +0000 Received: from mail-ej1-x62b.google.com ([2a00:1450:4864:20::62b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rdNYC-000RnS-Er for pgsql-hackers@lists.postgresql.org; Fri, 23 Feb 2024 04:52:47 +0000 Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-a26ed1e05c7so57858066b.2 for ; Thu, 22 Feb 2024 20:52:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708663964; x=1709268764; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=r11UHRzERq0hGbqHTPJMI9SoSKEZhA0WqrIp2cBeoHY=; b=Sv7/qAdoM97Um0Y6NpotHZGjbqH6wmK8RrKJQYtJBrpBButuYUrqlvR8yYO0TcEdv4 JDiB2nS/WdphgA+0zBEgRLL9I3jJocnbimJQeR1FP5HYeK/vpaN1Az+3DpfrdTJZK3v+ A8BgtE8yzk8yCtkEqW+WrSSH/FgVjlVAOOLfHfhpa7JmWyJeliCdiNk/c93h9bvfzAs+ B6A5TrcKQ7+wpZYEW967Ozmt3XgMkH2Ffnmrcet6NSiWysN0GnLhV4PCyRrlGlW1RXvg TL/mPM/BnKsU36OU3NEaDlalqp3BXvZNGgQ50qRyrxkZyz3nYNkiUMyYbjOqtshD4WJv e3Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708663964; x=1709268764; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=r11UHRzERq0hGbqHTPJMI9SoSKEZhA0WqrIp2cBeoHY=; b=ac6Xp3hQk3xabiOru6ESGEPhp9Wul/8PuKsLp4QuY4ys/DCMEqultHGqRFFoTa4kN9 EnbV4NtU7nqFfQnqsHduBypcSNbePoNP+DzQlL8z6ce+pUxg5B1JXnrd5DY1zxk7YPNB M49u38jw6fpU+EpCX19PWxHFmKbRMni0mKAgKp/zlsdb0spYUAsOS1uNTvaBqk9iJNj/ Tn9tjTMN1D+95Rqhl3NbnG6JOuSK0aMy7w1d/XFgYQucQpbnMOHJ6oWc1G17U2b9L8PL QYNPICXwm2xc646bbWBJIB2Jj7I1Nljjp9rmRzktvcgWblgNG+pLUP93WYjFrJU76fwz hDfA== X-Forwarded-Encrypted: i=1; AJvYcCU90eGVZHYRa0JdywWzRUxiIYShXwIH/ZW7Nh7HviAs7NsLlOvnRzxGvSCJ/5Mh6ojvxI2TCCqnOhckcO+1ZaiuHAvtlutKw1Nw3rOuXpqkz/+i X-Gm-Message-State: AOJu0YwpPjEigM4sE6s93EUKyYT5X7K9f76O93A8N1eg/yr+dxlZnxhb bdOXuxCJiS62rusXzZEJWJYADM/e1MN0mUf7Cjf4AVZs4lDieXv+v0HdtoOZXycLySBtWk8NRA2 LCfn+uwBfdGmZH1wsUHhy/qJXP9U= X-Google-Smtp-Source: AGHT+IEHRMJgZyZy2v3RRAQARfg9ibp6aFnGNVTQtSRkKlhOqPOp8KiJB4jnRFhNHSnEGf06sI8dpGElFvobXVdjTqw= X-Received: by 2002:a17:906:bc4d:b0:a3e:f7ae:49b6 with SMTP id s13-20020a170906bc4d00b00a3ef7ae49b6mr409524ejv.49.1708663963755; Thu, 22 Feb 2024 20:52:43 -0800 (PST) MIME-Version: 1.0 References: <61b4add9a01f21011789b6ee04085751@oss.nttdata.com> <3d5fd6d955944b5e8e4b8d1917f14885@oss.nttdata.com> <67fac921c935d7b9db51609a7599520f@oss.nttdata.com> <20240215185911.v4o6fo444md6a3w7@awork3.anarazel.de> In-Reply-To: From: Robert Haas Date: Fri, 23 Feb 2024 10:22:32 +0530 Message-ID: Subject: Re: RFC: Logging plan of the running query To: James Coleman Cc: Andres Freund , torikoshia , pgsql-hackers@lists.postgresql.org, =?UTF-8?Q?=C3=89tienne_BERSAC?= , ashutosh.bapat.oss@gmail.com, rafaelthca@gmail.com, jian.universality@gmail.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Feb 22, 2024 at 6:25=E2=80=AFAM James Coleman wr= ote: > This is potentially a bit of a wild idea, but I wonder if having some > kind of argument to CHECK_FOR_INTERRUPTS() signifying we're in > "normal" as opposed to "critical" (using that word differently than > the existing critical sections) would be worth it. It's worth considering, but the definition of "normal" vs. "critical" might be hard to pin down. Or, we might end up with a definition that is specific to this particular case and not generalizable to others. --=20 Robert Haas EDB: http://www.enterprisedb.com