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.96) (envelope-from ) id 1wOox5-000CZN-1m for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2026 03:47:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wOox2-00117v-2l for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2026 03:47:33 +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.96) (envelope-from ) id 1wOox2-00117m-1r for pgsql-hackers@lists.postgresql.org; Mon, 18 May 2026 03:47:33 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wOox1-000000007ga-0JBI for pgsql-hackers@postgresql.org; Mon, 18 May 2026 03:47:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=4MVaylBFAvR1VQsxZT15VGvug2/s3cnu6yduLFh5JcA=; b=GHcOpSYyJDOKXmJ/rrkeyP5+/J yNjMw1L6fc1ABiiLsGQA+7anE2xG/5nlJN0C7shxEYZ4g0mxxgaURPJyDV4VR1RcYatlwecvca6dH 06QereKzW/Yyih6bWd4NWCZBVd7QVoa/MZHkqsESgJXOoL3SHObFU6/0Q1nAr6ktZGsr0YR9mFetN Hu6QUGdf3JCal86PpXjv4pdNb1ozM6qgZFKuyyTteccqeLh4NpG3NAKwj6A8NVeXvoxOusnITBRGT q6EtwVfEgoHBecbcQsyx3mWRbLd4QNldhwzS3rGw1jbxgNNtP2KCBlN+7GdY7bhywO956UbDbiOW1 1uBrgbmA==; Received: from [2409:11:4120:300:356e:90b7:ad1d:2644] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wOowy-000Ete-2C; Mon, 18 May 2026 03:47:30 +0000 Date: Mon, 18 May 2026 12:45:51 +0900 (JST) Message-Id: <20260518.124551.2123531993096182264.ishii@postgresql.org> To: li.evan.chao@gmail.com Cc: pgsql-hackers@postgresql.org, ojford@gmail.com Subject: Re: Should IGNORE NULLS cache nullness for volatile arguments? From: Tatsuo Ishii In-Reply-To: <20260515.163425.1708559652740041584.ishii@postgresql.org> References: <20260514.215622.2237422742023167912.ishii@postgresql.org> <20260515.163425.1708559652740041584.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:356e:90b7:ad1d:2644 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk >> Yep, good idea. Addressed in attached v2. > > Thanks for the v2 patch. It looks good to me. I am going to push the > patch within a few days if there's no objection. Patch pushed. Thanks! -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp