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 1tDQpb-000ePm-L9 for pgsql-general@arkaria.postgresql.org; Tue, 19 Nov 2024 16:11: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 1tDQpa-00EIlZ-BM for pgsql-general@arkaria.postgresql.org; Tue, 19 Nov 2024 16:11:58 +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 1tDQpZ-00EIlK-Vj for pgsql-general@lists.postgresql.org; Tue, 19 Nov 2024 16:11:57 +0000 Received: from mail-wm1-x333.google.com ([2a00:1450:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDQpX-002ipH-Dh for pgsql-general@lists.postgresql.org; Tue, 19 Nov 2024 16:11:56 +0000 Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-43161c0068bso29794095e9.1 for ; Tue, 19 Nov 2024 08:11:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732032714; x=1732637514; darn=lists.postgresql.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=vHS33iIfU7G7vUjASE5M+13dttO/md+sNWS7Zw6ypN0=; b=BNSD8HCf8wUcaSlzEFanYHf80EKIdaPDv9y/T+zG8miaSOL7gjjmrQ8BE4nZ4sVh1M VbYhmTOsKR/PKGHzK1NKyLYvRHo+cTjo+XTPJmSxwItoUHy87uJgDuqbqk+gm3rG8Nr4 VDP+EO/IpfbLu+FJ/USb+A3Hnsx6hRPHY8UryLbce8CJ5l1ybauACr1eRDE/OpDU1/Kx 3j/rwFq5PkAApsxvXF27rs330jK24LTTlRdyAqkzrzM6Jtclh0bhVvv7/WaNX50eyvvL gmhfypcEA0Qu+3NqeMTj2F7dA3cE1rZvN8cNCrLbgRQymFMIF/z7+ISb5SQti8oFZ577 YZgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732032714; x=1732637514; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vHS33iIfU7G7vUjASE5M+13dttO/md+sNWS7Zw6ypN0=; b=Oe/eJDHe+wa6KyIsYG2GLAIJ6KKYP/AhkSqBeaN1G0s8Qkc34Ja1tqzmw2lHw0dc25 x3/YAay6F8lLt5efZwqtOxcoboLf4J+89Jk3VLM7/0FUocLdH13QuT4ZErT54hoV/3LH 07sXRzlM/pgOXF97czKW2iNcXkD+0xnyEIr14K1a99DZoIIlhu8OvR3uFCvvVDYkmnzm Rv/9JheybczE4Rf6CzPYYh3i8n0qvVkZ5LYxKUAdpbPZQDF5BHXfAW4JJR/rqbTojVq6 LXlLjwcgY7xMhFnPuTK0r23KKR/tjJQs0MJ/FvbaryCEJ8xddWzGJK+T44B+jf8fkcAQ 7knA== X-Gm-Message-State: AOJu0YytYjtt+78cqt40DIBPMFBRgbmqWi483r/NTdSUhO1wGUVm6Vhc RYdO1RXzRKlq2ubrcrYo6Z/umEcfKIlNqDsFLTW9r7pMENgpXAUTE+lNCA== X-Google-Smtp-Source: AGHT+IFKWUIZB7Kju9jNN5An7IOuwSiUoxf9tQyVqaZJRq4ntYkDgd84qHS3x+qS9x+WMZSBz78PPQ== X-Received: by 2002:a05:600c:4f06:b0:431:5533:8f0b with SMTP id 5b1f17b1804b1-432df78e7demr123559175e9.32.1732032713760; Tue, 19 Nov 2024 08:11:53 -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 5b1f17b1804b1-432f642f15esm26058335e9.0.2024.11.19.08.11.52 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2024 08:11:53 -0800 (PST) From: Paul Foerster Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints Message-Id: Date: Tue, 19 Nov 2024 17:11:22 +0100 To: pgsql-general list 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, the PostgreSQL 15.9 release notes instruct to look out for especially = detached partitions with foreign key constraints. I'm in the process of = updating our databases from 15.8 to 15.9 now and found a case where the = select statement returns a constraint. The release notes say nothing about when to fix that using the generated = add or drop statements. Do I want/need to do that before or after I exchange the software? And = if it is to be done on a particular of the two releases, why is that? https://www.postgresql.org/docs/15/release-15-9.html Section E.1.2, changelog entry 5. Any insight would be highly appreciated. Thanks in advance. Cheers Paul=