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 1qsfXj-008s5z-Oc for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 08:35:12 +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 1qsfXh-0083L0-QN for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 08:35:10 +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 1qsfXh-0083KY-Bt for pgsql-hackers@lists.postgresql.org; Tue, 17 Oct 2023 08:35:10 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qsfXe-000tA8-P5 for pgsql-hackers@lists.postgresql.org; Tue, 17 Oct 2023 08:35:08 +0000 Received: from [10.10.20.88] (node-9fc.pool-101-109.dynamic.totinternet.net [101.109.47.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.lepikhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 55879E20E62; Tue, 17 Oct 2023 11:35:02 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1697531704; bh=oTTDsbjGk0zYl4yDcoh0fqv2xvg3wAbbcBNO4UCXfeM=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=JYLSWV1bOs8KiurRT34+sAb+IlvN93DdZSprga+H6l1Hoflo00blsVVbZsG/qAjB0 eb1W6H0hbpOo18vFZ4GAxl7muHWsCnuXF/879t/oNlQdN3XLUohiH/Ob8TnCPmYaFs Z0NIJTNlbP4a/iAnO90uGA0pj6i21UUIP2JaG3zEZd38PGHv+88uE752bafn6ian9j ZJErhV0pq1fNXz2rbGXrnaxIse+clA/jEBSMdf2UKFj0saV+olgHXq5OE/yTfy8VTm 6+Rq7vji8DSm1Lw7R2wVoHrdD/4Si8Q4Yk7E/FherkV1vECoMZxW9hYyPz0r/gcXpC i9PI5qjaYeKjQ== Message-ID: Date: Tue, 17 Oct 2023 15:34:59 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Asymmetric partition-wise JOIN Content-Language: en-US To: Ashutosh Bapat Cc: Alexander Korotkov , Alexander Pyhalov , Jaime Casanova , Aleksander Alekseev , pgsql-hackers@lists.postgresql.org, KaiGai Kohei , "a.rybakina" , =?UTF-8?B?0JHQtdC70Y/Qu9C+0LIg0JTQsNC80LjRgCDQndCw0LjQu9C10LLQuNGH?= References: <163118104689.1167.8241611097516113795.pgcf@coridan.postgresql.org> <20210909153833.GA6514@ahch-to> <2c9caede-55c0-2042-e421-dd0021f28837@postgrespro.ru> <792d60f4-37bc-e6ad-68ca-c2af5cbb2d9b@postgrespro.ru> <88bc3c051d285653215393a56bdf3056@postgrespro.ru> <5c0e38e3-7ab5-4b10-a1bb-70ca69771ff0@postgrespro.ru> <521c2a71-49dd-4ab5-a585-569d0af3a647@postgrespro.ru> From: Andrei Lepikhov Organization: Postgres Professional 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 On 16/10/2023 23:21, Ashutosh Bapat wrote: > On Mon, Oct 16, 2023 at 10:24 AM Andrei Lepikhov > Whenever I visited this idea, I hit one issue prominently - how would > we differentiate different scans of the non-partitioned relation. > Normally we do that using different Relids but in this case we > wouldn't be able to know the number of such relations involved in the > query unless we start planning such a join. It's late to add new base > relations and assign them new Relids. Of course I haven't thought hard > about it. I haven't looked at the patch to see whether this problem is > solved and how. > I'm curious, which type of problems do you afraid here? Why we need a range table entry for each scan of non-partitioned relation? -- regards, Andrey Lepikhov Postgres Professional