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.96) (envelope-from ) id 1wCZho-0027gP-20 for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Apr 2026 09:05:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wCZhm-00AvJI-38 for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Apr 2026 09:05:11 +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.96) (envelope-from ) id 1wCZhm-00AvJ9-1j for pgsql-hackers@lists.postgresql.org; Tue, 14 Apr 2026 09:05:11 +0000 Received: from mail.postgrespro.ru ([93.174.132.70]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wCZhk-00000000whF-1VaL for pgsql-hackers@postgresql.org; Tue, 14 Apr 2026 09:05:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1776157505; bh=Jd2gbZ6GInPrA+w3O3A5ivNgHoWgm/yC2DivRvJgyXU=; h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To: From; b=FSxt0gfuOzl10H6VBIMeglnZQZIfpx79Xfr9De8EDcf5xGzA/T00FNpZFlqYJevgc hIuF/l9RJLN6VxsONerQOQ91AXWlblGTZ1Q/9wce3MOvpvLfcx1a0f0itzG0sLqYEI Jp4r/X7Ex0TNXzquCxqde3eRHRygWGG9Vu/ZRgQ0ruXOMxB3TZrIztdvqWUgJICDGw iOHMT5cNiDNIbi7DnOrJG4RJEMQ/PjjAhphzMWjPCVKSk7KkOmHkUShOS/CQSlfoHq mfvutiQfCMpfelgNvfh4HuyONm112+iqbJ7DBkOCa4nN25pFvaSe3evYDAfKssAMiU vpruiB/n7vSbw== Received: from [172.30.48.234] (debian11-template.l.postgrespro.ru [192.168.2.254]) (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 0AC435FFA8; Tue, 14 Apr 2026 12:05:05 +0300 (MSK) Message-ID: <414c3430-77a9-438e-9dc0-c66033f6be63@postgrespro.ru> Date: Tue, 14 Apr 2026 12:05:04 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. To: Matheus Alcantara , pgsql-hackers References: <31d04a1b-c0cb-4e6f-a344-0db048a3b673@gmail.com> 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: 2026/04/14 08:38: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 3.0.0.9059, bases: 2026/04/14 08:44:00 #28397241 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 Hi Matheus! Thank you for patch. I agree that dependency should be automatically added for SPLIT PARTITION. But I'm not sure about MERGE PARTITION ... Might be it would be more correct to automatically add a dependency only if all merged partitions have it? -- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com