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 1sTl4L-00271U-J2 for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jul 2024 16:30:25 +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 1sTl4J-002VE1-Om for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jul 2024 16:30:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTl4J-002VDt-DK for pgsql-hackers@lists.postgresql.org; Tue, 16 Jul 2024 16:30:23 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTl4G-002MwY-Sl for pgsql-hackers@lists.postgresql.org; Tue, 16 Jul 2024 16:30:22 +0000 Received: by mail-io1-xd34.google.com with SMTP id ca18e2360f4ac-8046f65536dso302819939f.1 for ; Tue, 16 Jul 2024 09:30:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721147420; x=1721752220; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=PStwZfrKIQGNkYTamvLhSmfWRQ0JxeS4RxJHLdxmsXg=; b=gSg4TBfLBVEWdNavNBmJTGrHMlBQ59HolP3GIDOzDLwWyMdCfO+x960CaFKR9J4M3h npA4GsLBkAQBWBPmX+Od5xGKh6mboq3zCzWoYcEztMLSkOGzH7dY51oz6q1mu2rCv8W5 UDLTIRPiV7FQlFQy+gFajWe0JmeEDGFogBfLhgjrcp4T71jCGdpf5K0zYbk54UmXBqrH tv1dzdlhnZPp5CVmUMQIR7haXW3mFZPofK5zS4BahPUKyjJ98vQesigKOhA3/Ojto51I TvW4ZjrqJ8tbTtozHkWY36RqPYZHUu5IRZa8ecuAsOQjWnH2nAKljtd7pIYBxCe/h8z+ QzfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721147420; x=1721752220; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PStwZfrKIQGNkYTamvLhSmfWRQ0JxeS4RxJHLdxmsXg=; b=R++iNfT4pbKZtgKJy5aOOT9Yx/CdjmfxaCFD2cAuvxAT0K0GbHYmDerJB1oDn1LMLd j7UMV+gb+RD5iwn4MFmyC3MQsL/u1RiiMiqHL2O7Ly/q6zL7nbrS+01ZXWu55baDV15N nlq/rT1Cdlh/vNtstzjqCEzM8OaXjVnqMnMXbb7BBGznqNx8nfntShZ3JXUYC9H3bsWg 37+ldLfCdYm3gEr2kpoWtVWCAlQjWOLbOcNUgxmLQ9vxlJT2kUWZomsv28bEwswC83hI +33Tt8ckS1de3ScEy3w3UgkMCxZn5YlgB4Hh7Im2ViO4TkOdvvfcGIfToE2THSezAQho bCvA== X-Forwarded-Encrypted: i=1; AJvYcCXhevYv5xKRmQXx+/SU1xpgBPDKzqi7fbAuhjyUBg7dfkeml2YLtXLbzpeiIC78bfYF15GIb4j2brxdrru6tsXIdnJlL9TFwyalhtzvZkKDFHV7 X-Gm-Message-State: AOJu0YyRbqnxc/nUd0HancmneEnXmpqFPLlnoZJId5rG9HwuE5C6OduH b0JMtB9cCeh9S5ZApC/jW8rOv6MYmsoChZZHQRoRLdk/RkgZHvZO X-Google-Smtp-Source: AGHT+IGv2Ojtke5kojVwzx/YyVczFqUAfMP3FXfGgmq8XQUElbEhU6APbpjLq/EFTa++VuQj2ZoZYQ== X-Received: by 2002:a05:6602:6019:b0:7f6:853d:de8b with SMTP id ca18e2360f4ac-815765186c1mr382391239f.14.1721147419745; Tue, 16 Jul 2024 09:30:19 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4c20cd72c62sm188098173.129.2024.07.16.09.30.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jul 2024 09:30:19 -0700 (PDT) Date: Tue, 16 Jul 2024 11:30:17 -0500 From: Nathan Bossart To: Robert Haas Cc: Fujii Masao , pgsql-hackers@lists.postgresql.org Subject: Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal Message-ID: References: <8a668c51-c6af-4744-a978-c6a2ce3b1d83@oss.nttdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Jul 16, 2024 at 12:23:19PM -0400, Robert Haas wrote: > TBH, I don't want to do that. I think it's too fragile. It's the sort > of thing that just barely works given the exact behavior of these > particular GUCs, but it relies on a bunch of subtle assumptions which > won't be evident to future readers of the code. People will very > possibly copy this barely-working code into other contexts where it > doesn't work at all, or they'll think the code implementing this is > buggy even if it isn't. Agreed. If there was really no other option, it would at the very least need a humongous comment that explained why it worked in this specific case and is unlikely to work in others. But it sounds like we have another choice... -- nathan