Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n050A-0006Dx-AR for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Dec 2021 17:02:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n04zd-0008U2-7r for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Dec 2021 17:01:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n04zc-0008Ts-TB for pgsql-hackers@lists.postgresql.org; Wed, 22 Dec 2021 17:01:32 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n04zX-0001CU-BL for pgsql-hackers@lists.postgresql.org; Wed, 22 Dec 2021 17:01:31 +0000 Received: from [192.168.0.192] (unknown [77.222.120.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id B1C3721C1DFD; Wed, 22 Dec 2021 20:01:22 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1640192482; bh=lJ0o+TucWT9633IjgGGOdLBr3qwFKVnvBUbvx0tHKqs=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=PHmiWfPtpfdKfFp2yBuzP0wN1SynPBC7OR8e/edV4kvopRJxZwuu5TVqi6zu83f1i w29NS1mO7eMp06e/j6ON3Bn8wvZCoSgatRBwIuRssuQxso4qO5enQhm7SYsxG0vCqW cOFg3o+FvmcfJXPS2A30X560g0qt0L+oRncAU464= Message-ID: <39d9f8f2-19bb-c9f2-572e-06694fe9b829@postgrespro.ru> Date: Wed, 22 Dec 2021 22:01:22 +0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: Clarifying/rationalizing Vars' varno/varattno/varnoold/varoattno Content-Language: en-US To: Tom Lane Cc: pgsql-hackers@lists.postgresql.org References: <15848.1576515643@sss.pgh.pa.us> <26144.1576858373@sss.pgh.pa.us> <25142.1580847861@sss.pgh.pa.us> <36b509ec-2b71-c1d0-d726-f3e15cbf85b2@postgrespro.ru> <242720.1640187764@sss.pgh.pa.us> From: Andrey Lepikhov Organization: Postgres Professional In-Reply-To: <242720.1640187764@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22/12/2021 20:42, Tom Lane wrote: > Andrey Lepikhov writes: >> On 5/2/2020 01:24, Tom Lane wrote: >>> I've not written any actual code, but am close to being ready to. > >> This thread gives us hope to get started on solving some of the basic >> planner problems. >> But there is no activity for a long time, as I see. Have You tried to >> implement this idea? Is it actual now? > > It's been on the back burner for awhile :-(. I've not forgotten > about it though. I would try to develop this feature. Idea is clear for me, but definition of the NullableVars structure is not obvious. Maybe you can prepare a sketch of this struct or you already have some draft code? -- regards, Andrey Lepikhov Postgres Professional