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 1tdnEx-009Vw7-H3 for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2025 09:23:07 +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 1tdnEw-00GssP-6Q for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2025 09:23:06 +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 1tdnEv-00Gsrm-SL for pgsql-hackers@lists.postgresql.org; Fri, 31 Jan 2025 09:23:05 +0000 Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tdnEt-002REX-1z for pgsql-hackers@lists.postgresql.org; Fri, 31 Jan 2025 09:23:04 +0000 Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5dc82e38c10so952542a12.3 for ; Fri, 31 Jan 2025 01:23:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738315382; x=1738920182; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=hQy6aIhgDzlDz+n2vQEW16HZRr3DHddVgrY5uUHxwOU=; b=FslAuHY98qG6hSvxs7UwTaVNmGIw5k9ER7d4kB46ovGqtaZBpaavE/HFwvW8aK+R2M E3iapz6PJfV5JYKbMPlFGlTATt2c2Y3M5Cz9r3Cvwtjv7vNr70b6tM6hMFn//1sTdgwI 5tMdeWBHVda40WNqIOHACQlwV5DjaNQgnldvNJ9nkTWIjZNJGUfSBxOV9H/Rac+rxyZ7 UVxpBvVvgGYBR8tjvM2wICUoOUncmxACbKdpSq+BfKLSdMiDTqpwvxWC8O4m/jkPLr0W YaSen5c7qmJnMjGeeVWDTApiZoRdowH4h1vtS6f9nutthjxI7/wP2oo0qx55goqyMWCN tVqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738315382; x=1738920182; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hQy6aIhgDzlDz+n2vQEW16HZRr3DHddVgrY5uUHxwOU=; b=i6m+QhQ8HRB0Ut0whghHA7E8eXsPGHUWU/s37wYA4rVCBjjE0avcIEmKHl+2zNYqEp HuyP0Ic95Jb2TEdOGvQOghaxrjDzjZjD9iXNrcDOOEJoPQNR+l8HW85JREJK1hsC07mM fM9Fe7UtSCEM7ZVbhvBDYXxw5g2Hzb0OtoeEJTSXzq9Wykm6poRcHfL9AeaWrF04XFWg Hubphmjf7zlugzK97J01f597mVACmUapryxRgBnVT3qrdsh+Ot31sYl1vQfplaqWffru J5bo88bE0ED4cBvnJFsYin7M1KdZWQuecOdCAe3nkmDPr+87yQ9sTsLaUyTK6BxQsKDn Pesw== X-Gm-Message-State: AOJu0YwGTHbaT2pnGs/K/eaOTN/H+0zlXQnOEKdnZWsPXWTGcx8Rj9ZR CvA2tNBTDgDh2aUKZQJyj53gAECJF//ylY2o/uc2hhsNRFCKHiI5yOxPD9f19sT5h4uY01JyRfn Vi6L1Fu2fgfK4ntneMLLjbc0rhSNgw2VIBII= X-Gm-Gg: ASbGnctZ92NZa7aSZ+BEtFZuu9GziS15CHZGd/40DW7t9cWoEdtxG3eVibUnGnrNECp Um7E0ja5NO8RGex1k9Mq9PzOtNxP0BbtYtNNWJ13PyQa9P/wsa/470KsQg7ay6/ldEphPAn8q X-Google-Smtp-Source: AGHT+IHCyN53lMfJ48j9GgNEW3UEh81MKCGfLEvwnMnYJK8Zrf4Og+FGMfdV3FWC5dsDUt54HLwqoQ9WxWOtklWXfBw= X-Received: by 2002:a05:6402:ea7:b0:5dc:80d5:ff23 with SMTP id 4fb4d7f45d1cf-5dc80d60538mr2206004a12.15.1738315382324; Fri, 31 Jan 2025 01:23:02 -0800 (PST) MIME-Version: 1.0 References: <171085360143.2046436.7217841141682511557.pgcf@coridan.postgresql.org> <859476bf-3cb0-455e-b093-b8ab5ef17f0e@postgrespro.ru> <4e2764f7-f6be-478f-8d7f-f921dbd10f5f@postgrespro.ru> In-Reply-To: <4e2764f7-f6be-478f-8d7f-f921dbd10f5f@postgrespro.ru> From: Alexander Korotkov Date: Fri, 31 Jan 2025 11:22:51 +0200 X-Gm-Features: AWEUYZmnHtqMBv6aX5C3utkRPErgvCV5uXUy5dMmKn8f_MCitzg72PwOiHYxN_k Message-ID: Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands To: Dmitry Koval Cc: pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Dec 9, 2024 at 11:01=E2=80=AFPM Dmitry Koval wrote: > >I see fixes for the issues mentioned in [1] and [2] are still not > >implemented. Do you plan to do this in this release cycle? > > I would like to make some changes, but I think it would be appropriate > to discuss these points first. > As far as I understand, there is currently no clear opinion on how to > implement [1] and [2]. > > > I would appreciate your opinions on what improvements are really needed > and in what order they should be implemented. Please, check my thoughts on how this patch could be further developed. Given amount of work to be done, I doubt that'a a subject for pg18. But I think you could continue this work, and we could consider it for early pg19 cycle. Links. 1. https://www.postgresql.org/message-id/CAPpHfdtSxrcxQERO82cyQ2heN3%2BA7VC= 63k8SmL%3DEEiph-8rfHg%40mail.gmail.com 2. https://www.postgresql.org/message-id/CAPpHfdvVMdUX0DGSK3oAbt9C5TPup%3DB= Eq8QkmvDrMbuD4BR9Fw%40mail.gmail.com ------ Regards, Alexander Korotkov Supabase