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 1qqVDw-00AdLL-8B for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Oct 2023 09:09: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 1qqVDt-00EUkI-FR for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Oct 2023 09:09:46 +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 1qqVDs-00EUjt-W9 for pgsql-hackers@lists.postgresql.org; Wed, 11 Oct 2023 09:09:46 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qqVDm-001REt-Ob for pgsql-hackers@lists.postgresql.org; Wed, 11 Oct 2023 09:09:45 +0000 Received: from [192.168.1.3] (a0.sub235.net78.udm.net [78.85.235.0]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: s.glukhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 6CFC3E20EA1; Wed, 11 Oct 2023 12:09:37 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1697015377; bh=lMrOlt5o8QGJPSfxIY7xHBaiby0ROipUZdjYB28aLg8=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=vVDxzOzd71rE6dnxVBXb/jG8wzFouYs/U8VsEltmJotIr6OTtEdbEcCih1r7OYmvq 3m0WnxXZOzAvwEXPJ/xvxdl5GY8bP7RJKr5f+RdRI09RhH5exrJ3+vy30VlEUixuUz Lu0aDIP8qUb5DnjZrEeETBK42KlegQKSw2WdphNFLhrzaAApjhAfKvnsTnpatHi5ek cbptDCzU9nxb78BjcjiTocLvkPn3aCnxkNFkvgnnhAc1E7MPwbPiAf0vEvEuUS28aO 1ZS5sZ7oTKePVwkZb7aZEamHdZwhmL3Gdl2WpwY1+nFlVZRjyzS7kf5UkM5x/HsoDW z6nCBs6QdX9BQ== Message-ID: <5845262d-9b6a-71f7-3485-c06e4977586f@postgrespro.ru> Date: Wed, 11 Oct 2023 13:09:36 +0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: Problem, partition pruning for prepared statement with IS NULL clause. Content-Language: en-US To: David Rowley Cc: pgsql-hackers@lists.postgresql.org References: <2f09ce72-315e-2a33-589a-8519ada8df61@postgrespro.ru> From: Sergei Glukhov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Thanks for fixing this! I verified that issues are fixed. On 10/11/23 11:50, David Rowley wrote: > I'm aiming to commit these as two separate fixes, so I'm going to go > look again at the first one and wait to see if anyone wants to comment > on this patch in the meantime. Regarding test case for the first patch, the line 'set plan_cache_mode = 'force_generic_plan';' is not necessary since cache mode is set at the top of the test. On the other hand test scenario can silently  be loosed if someone set another cache mode somewhere upper. As you mentioned earlier it's worth maybe adding the test for run-time partition pruning. Regards, Gluh