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 1scoTe-00AeRl-UL for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Aug 2024 15:57:59 +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 1scoTd-009YME-1i for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Aug 2024 15:57:57 +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 1scoTc-009YM5-JG for pgsql-hackers@lists.postgresql.org; Sat, 10 Aug 2024 15:57:56 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scoTY-0043if-Rn for pgsql-hackers@lists.postgresql.org; Sat, 10 Aug 2024 15:57:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1723305468; bh=KqlevMOxQkyrrXbnDr95cg62B+xyNGv9eBUoysifT4s=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=rjU27Sb/LI9lMFTb6Iq04poClab4/lkUNtz+rjzlO18hWL0s08XwWmAoNnfvi9opz 738BL0T7HDfYUhOP2yJd/mCEzyD3/3Gc+Oz57YOh2xcI9aEd+5JgwO1f/4hF44ASs0 6TXU9vo3BN+xZOdNdZ2a4bCjHMQHRncNhQrWuyU1ilcASvoSHNIauNV+fO/WKZssHX /PqVbkjI+7M6Jn8PL3ixBFtm2jHyE8xD+rzTTBYkL8sDVImRoGD4NOTRVy59H4mIGo BaNag4TRsyozQixACUUvSlku8xZNZ9+MVfPMYbx8dMcR53Bg0KtSkigt35ym+LyU5z lsIlu2vzY3zCQ== Received: from [172.30.2.66] (unknown [172.30.2.66]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: d.koval@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id A4F19601F7; Sat, 10 Aug 2024 18:57:48 +0300 (MSK) Message-ID: <768cbb42-d3f8-45de-89ad-72861f078dc2@postgrespro.ru> Date: Sat, 10 Aug 2024 18:57:48 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands To: Alexander Korotkov Cc: Noah Misch , pgsql-hackers@lists.postgresql.org References: <171085360143.2046436.7217841141682511557.pgcf@coridan.postgresql.org> <171085858750.2046434.12246066729700037354.pgcf@coridan.postgresql.org> <909e16b4-9eda-435c-b033-8294ae4adc05@postgrespro.ru> <3a4b9c1c-3edf-4e29-9629-b4113aefb0f3@postgrespro.ru> <20240808171351.a9.nmisch@google.com> <19c1e04c-2012-4475-8460-821dd633a6ce@postgrespro.ru> Content-Language: en-US From: Dmitry Koval In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-KSMG-AntiPhishing: NotDetected, bases: 2024/08/10 15:28:00 X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2024/08/10 07:47:00 #26267487 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Probably > QueryCompletion struct fits this purpose best from the existing > parameters. Attached draft patch implements returning oid of newly > created relation as part of QueryCompletion. Thoughts? I agree, returning the oid of the newly created relation is the best way to solve the problem. (Excuse me, I won't have access to a laptop for the next week - and won't be able to look at the source code). -- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com