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 1tGuzA-001l0X-HZ for pgsql-general@arkaria.postgresql.org; Fri, 29 Nov 2024 07:00:16 +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 1tGuy9-004nGA-18 for pgsql-general@arkaria.postgresql.org; Fri, 29 Nov 2024 06:59:14 +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 1tGuy8-004nFy-MW for pgsql-general@lists.postgresql.org; Fri, 29 Nov 2024 06:59:13 +0000 Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tGuy7-0006aQ-5b for pgsql-general@lists.postgresql.org; Fri, 29 Nov 2024 06:59:13 +0000 Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-434a852bb6eso13941515e9.3 for ; Thu, 28 Nov 2024 22:59:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732863551; x=1733468351; darn=lists.postgresql.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=pFOdxME2R//FjxrMYwLoZWstJ1ijIru1795wKQRartA=; b=QBA0sZDFVHCHPfvTvB+wC1SsgTx7ozB5OTQD0VdbXpAJ/1vDpvXRM0rPShGbfEFpTG iX2xzUwKUlTsy8sLjM7BbNe5q4bRCjZwlVWs/5ArezO5K7fhq6+qnhebJw8pRmKjgLwW x3wFjBGNQN+nCFuqm5tZRiAMK1tgIM0B3hNqbr682arVxxGrl6ng0HjcRPXBS8x69HQi DynHKjf5UVDxiyhyuWjL2CNsrwBpx6ewulS5MzrPDrX+216WE2KxZgP06KHiKIXnPQ5k WvF26ttcKXOJXyDhn9R89Tm7n+KisXFf357Oolet822ZexEk1MwcB9uc2CFxxI5ykYE5 7roQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732863551; x=1733468351; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=pFOdxME2R//FjxrMYwLoZWstJ1ijIru1795wKQRartA=; b=Tj1hlsPAkokdjvCPuDiT8DNgMtU7e8R+IZlGwnpUH3ccFGoQ5IE16N5LhCRKNAaXl0 i9jz6gwsucPtM9BBof3fCrky2El9xv0zSbhIuegfvb0yG+wPZrlAZx1aXExhsZ/328+8 WHDTQRDwE2jdQOD4ptb01Ao3ViTmOziftAUbbtOCimRQJ+U6ppOZqaLohcOlESI+f2Dd frHjB/SsNSg+cRJxs0qdqAKlG2C9+ydieUCoIs+pw1N+Fbx++DVkP6QUZLYmPfvHiGFC MauB9CGelSsfm4s+XCqOq45Rjod7lFcPnGuFybZzfK9uWslYsQaHQAzuEpBGJbANIyIB +g4w== X-Forwarded-Encrypted: i=1; AJvYcCUpcLTEVf8wIYDIH5G+SbS7QSMfa1zUetPYesc1cjZghHQWlBLERLFH5y1PKA79AM+mWd0jRt3apbm1Th7B@lists.postgresql.org X-Gm-Message-State: AOJu0Yw3AHUpqhPoRTtB3Xp9/DOnCAI/eXfjCfNcprJqsYAhgvwAr+Tq kSeo1GOmh55rtl3rvr8WJKY3o0EqcG7HHWjFVriUbsTIwu+NEt8M X-Gm-Gg: ASbGnctWzql+YrSe/xU2aN/NsGSxbdLqX9WLyN8XEtcAPLtCQuWVlHJ5igAleTZ3ckM RdMYXJoA4vOZu5e1IjfVKGv2QTsK1/IhniJAvVI11m63Y6k/4ra26WbijVskIAFAN02+x/GyH32 8BxN3jS5Ghf3ZzYB/7W5x3j2oYtR8/FWV7kspi06sG222K+0KwH9HqTj2IqUGc7kRIZiNeIz/mv 0rGyZ86Hcv2bfbA4s+7AAHQmsHF2eXAr7Syftfl44jNZA4CkVKlH13wf+Iw3B91psA110Rp6gvE EtonqRHY0Ehv07Ic/I1Au4TkqI4= X-Google-Smtp-Source: AGHT+IEX96lWg15J68DRxGWwh1PCeJ+ImJk11tMULtDT8qzdjUWKVxU7zJSFGaLSphyefCqOUPg3bA== X-Received: by 2002:a5d:588c:0:b0:382:49e9:9bd5 with SMTP id ffacd0b85a97d-385c6edb1e7mr8673146f8f.37.1732863550539; Thu, 28 Nov 2024 22:59:10 -0800 (PST) Received: from smtpclient.apple (143-45-239-77.dyn.cable.qlnet.ch. [77.239.45.143]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-385ccd3a580sm3569144f8f.53.2024.11.28.22.59.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Nov 2024 22:59:10 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION From: Paul Foerster In-Reply-To: <1900196.1732733556@sss.pgh.pa.us> Date: Fri, 29 Nov 2024 07:58:38 +0100 Cc: Adrian Klaver , pgsql-general list Content-Transfer-Encoding: quoted-printable Message-Id: <8DE45ACE-D7B0-4261-8003-7404518AC5A0@gmail.com> References: <5456A1D0-CD47-4315-9C65-71B27E7A2906@gmail.com> <78ec2af8-48f2-42c0-b317-cbb77cc5adc8@aklaver.com> <1723211.1732656332@sss.pgh.pa.us> <1900196.1732733556@sss.pgh.pa.us> To: Tom Lane , Alvaro Herrera X-Mailer: Apple Mail (2.3826.200.121) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Tom, hi Alvaro, > On 27 Nov 2024, at 19:52, Tom Lane wrote: >=20 > Okay, so I was able to reproduce this from scratch on HEAD: great, thanks. > I doubt that there's anything actually wrong with the catalog state at > this point (perhaps Alvaro would confirm that). That leads to the > conclusion that what's wrong is the release notes' query for fingering > broken constraints, and it needs some additional test to avoid > complaining about (I suspect) self-reference cases. In the meantime, I updated the whole company. The one test database = actually was the only database that this was returned. I found no other = occurrences. As I understand it, the worst thing that could happen is that one or = more rows end up in a detached partition table which should actually be = in another partition, right? Since there were no rows, no harm could = have been done. Also, since this is a self reference, the wrong table is = also the right one. Again, thanks very much for clarifying this. Cheers Paul=