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 1rZS1R-004N6g-JG for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Feb 2024 08:50:42 +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 1rZS1Q-0080d4-2X for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Feb 2024 08:50:40 +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 1rZS1P-0080cw-KQ for pgsql-hackers@lists.postgresql.org; Mon, 12 Feb 2024 08:50:39 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rZS1M-006mPU-Ft for pgsql-hackers@postgresql.org; Mon, 12 Feb 2024 08:50:38 +0000 Received: from [192.168.0.104] (unknown [62.217.189.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: p.luzanov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id DDBCAE20E55; Mon, 12 Feb 2024 11:50:34 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1707727835; bh=gHAyrscKHdiK+OJ7zBYJSCgMF5J6e/+cI0JDfpUyUt8=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=I8w8heTdDtc8OBThZ/Xcg+oAbNTj/LWBENdbVghko+wpyMhLnK1ZS6NX6uEQ6MRwu WKKEay5/HlxoHvwY5HiuU+JXE0qwijqM4f4o51e1Q+Nvv1GQ246pk3uPJ3eerurc9M LsxhzL20rKDQgZhLoNL72UAWM700WTJI1Fp6/c8Zz3/w5EcI96p6r9qnNOn4397zbf GNRr4aH10M36CT5zu36i3r1PjwHd2QK0ipv+oyc+YpZ3yZhA/D5ml29DSg/djfwHt8 QykWY1SZtVT28tzcR1k/nvH3ULrgEY5sTasN1CTuU1/sO0CgEU+6wnOrn1hzX1Veng KK5nvVJHR21kw== Content-Type: multipart/alternative; boundary="------------Ezatr2OixZmES7wo7feMRxqw" Message-ID: Date: Mon, 12 Feb 2024 11:50:34 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Add semi-join pushdown to postgres_fdw Content-Language: en-US, ru-RU To: Alexander Korotkov Cc: Alexander Pyhalov , Tomas Vondra , "Fujii.Yuki@df.MitsubishiElectric.co.jp" , Ashutosh Bapat , Pgsql Hackers , Ian Lawrence Barwick References: <10b3408a0880462d2ec6e3a92a46800a@postgrespro.ru> <81d8befc64cfd7ccc4a3f3e5c6862f20@postgrespro.ru> <816fa8b1bc2da09a87484d1ef239a332@postgrespro.ru> <4d6b5ec7-1583-f253-c6d2-810602b4b2aa@enterprisedb.com> <3dd9320e01232eb931b747ed75a26cfb@postgrespro.ru> <334dfcc5-51a1-4f0e-a8b8-6f8263d140a1@postgrespro.ru> From: Pavel Luzanov In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Ezatr2OixZmES7wo7feMRxqw Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, Alexander! On 12.02.2024 05:27, Alexander Korotkov wrote: >> But the worst thing is that replacing AND with OR causes breaking session and server restart: > I haven't managed to reproduce this yet. Could you give more details: > machine, OS, compile options, backtrace? We already had off-list conversation with Alexander Pyhalov. Yesterday, after rebuilding the server, I can't reproduce the error. I have good reason to believe that the problem was on my side. On Friday, I tested another patch and built the server several times. Most likely, I just made a mistake during the server build. Sorry for the noise. -- Pavel Luzanov Postgres Professional:https://postgrespro.com --------------Ezatr2OixZmES7wo7feMRxqw Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, Alexander!

On 12.02.2024 05:27, Alexander Korotkov wrote:
But the worst thing is that replacing AND with OR causes breaking session and server restart:
I haven't managed to reproduce this yet.  Could you give more details:
machine, OS, compile options, backtrace?
We already had off-list conversation with Alexander Pyhalov.

Yesterday, after rebuilding the server, I can't reproduce the error.
I have good reason to believe that the problem was on my side.
On Friday, I tested another patch and built the server several times.
Most likely, I just made a mistake during the server build.

Sorry for the noise.
-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com
--------------Ezatr2OixZmES7wo7feMRxqw--