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 1sB506-00E9MC-Ca for pgsql-hackers@arkaria.postgresql.org; Sun, 26 May 2024 03:56:51 +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 1sB506-003H9N-Bg for pgsql-hackers@arkaria.postgresql.org; Sun, 26 May 2024 03:56:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sB505-003H9E-W4 for pgsql-hackers@lists.postgresql.org; Sun, 26 May 2024 03:56:50 +0000 Received: from mail-yb1-xb33.google.com ([2607:f8b0:4864:20::b33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sB503-000nQJ-0n for pgsql-hackers@lists.postgresql.org; Sun, 26 May 2024 03:56:49 +0000 Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-df771b6cc9cso2444525276.3 for ; Sat, 25 May 2024 20:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716695805; x=1717300605; 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=SshNdbhc/q7e2aXFMu2E5wwkOTCKJTnhe6datJvBQm8=; b=PB8sD34YLSWZejcwgd66/cRjk+cXBqaMw0yJFp3OnhyGHC55/CWUi0bKdDNz2umWvh kFP3nVcyk75Kbkys/lvJmYH7YifvAOB/cmMZXHlpTuKROXGsh7wwXNw0gKKKZAntacwH N9tbeb1MFqT4PtPGb1nq5PFOc9aO4U2+Wfrsi7S2mZtRxoSRq2/P38Eh5HidIHrR5Ohz C+7ws/YIbhmOw/sw6rdnsW+2BYd7Adq6TreIOeP17b1g1ABMwATlX0yxNLfT2i5poEKS cI8URSHK9eJ4ktthUCEUsd5Hd6jFP+Aji/kvCzmAh9VHWRVV/i/tGadrLJ9ElEuotOXL AskA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716695805; x=1717300605; 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=SshNdbhc/q7e2aXFMu2E5wwkOTCKJTnhe6datJvBQm8=; b=WQgDdwt8z4pySxs9vlqZpx+CQjO7f4+dQ7gbHaX+I6Y92oGa2VyGklt5ZfxNSXIaL8 +WcZjLrGK/gvcRA+ndXEaMqSrb8gxv2Kjyuc5n+mdyHjAvFwnSe99KdYUCkB1QNs5Hyl M8MLCm4ywiZogsXbkQeiekpV7VZxpw3l4DzERHrIjq6VNsSaTrr5GiKWDLZARtc172rF fWOx7phhwKB5ylTOHp3MkMV+5j4dqkWQGYZulgcE1J78vJ4oDQ1Id1vGEJLr+6MaYsqZ 8/AC0ALPtFxMrtWChht24Z6mbQjSFmDNCCQRTyT7dxERVyhwsktbhsVl+zNkYyMsNJfX e1Bw== X-Forwarded-Encrypted: i=1; AJvYcCUPQ5hLaj1s+Fp7Y+WvPQL9phZqjhJubdL1vNkqvC2YQiADiFRGWSW3oLR43h46GZEMT31vOzuX3ziFnJNDc7Yh8j4KtqZcx7JL0K60UralMMhM X-Gm-Message-State: AOJu0YyA4aMIWg2f2QM04WiWe5nNsI0xU7cy5y+LfOCKQJ1cBdUDrefl 87Gg/ClcYzC3VhwgcwaSfKRIn544Z732teqQezoCXkOObsWsPnxv68Fsu3V5KtwC0k4+t4mEVGW ihOIq4dm2jeBbYCe7WFgGu54XubyVYKpfo7s= X-Google-Smtp-Source: AGHT+IEJVMb7CTv3zRxtRIq/XNGd1ZBnfIs7PiISoqj1KFepB2U5wrOpWJqk9orCsiFrs56boy8ZF9nUs2Ymv73M8a0= X-Received: by 2002:a05:6902:2302:b0:df4:f316:e506 with SMTP id 3f1490d57ef6-df77218b58dmr9074874276.15.1716695805469; Sat, 25 May 2024 20:56:45 -0700 (PDT) MIME-Version: 1.0 References: <86bfd241-a58c-479a-9a72-2c67a02becf8@postgrespro.ru> <0f655bcd-6487-4179-f9cf-c248efbad510@gmail.com> <41117807-3bea-45bc-a9c0-743c29abff2d@postgrespro.ru> In-Reply-To: From: Alexander Korotkov Date: Sun, 26 May 2024 06:56:33 +0300 Message-ID: Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands To: Justin Pryzby Cc: Dmitry Koval , Alexander Lakhin , 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 Sat, May 25, 2024 at 8:53=E2=80=AFPM Justin Pryzby wrote: > On Fri, May 03, 2024 at 04:32:25PM +0300, Alexander Korotkov wrote: > > On Fri, May 3, 2024 at 4:23=E2=80=AFPM Justin Pryzby wrote: > > > Note that the error that led to "EXCLUDING IDENTITY" is being discuse= d > > > over here: > > > https://www.postgresql.org/message-id/3b8a9dc1-bbc7-0ef5-6863-c432afa= c7d59@gmail.com > > > > > > It's possible that once that's addressed, the exclusion should be > > > removed here, too. > > > > +1 > > Can EXCLUDING IDENTITY be removed now ? > > I wasn't able to find why it was needed - at one point, I think there > was a test case that threw an error, but now when I remove the EXCLUDE, > nothing goes wrong. Yes, it was broken before [1][2], but now it seems to work. At the same time, I'm not sure if we need to remove the EXCLUDE now. IDENTITY is anyway successfully created when the new partition gets attached. Links. 1. https://www.postgresql.org/message-id/171085360143.2046436.7217841141682= 511557.pgcf@coridan.postgresql.org 2. https://www.postgresql.org/message-id/flat/ZiGH0xc1lxJ71ZfB%40pryzbyj202= 3#297b6aef85cb089abb38e9b1a9a7ffff ------ Regards, Alexander Korotkov Supabase