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 1uKBZM-00FccH-4w for pgsql-hackers@arkaria.postgresql.org; Wed, 28 May 2025 07:51:24 +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 1uKBZK-00FK4a-07 for pgsql-hackers@arkaria.postgresql.org; Wed, 28 May 2025 07:51:22 +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 1uKBZJ-00FK4S-Lj for pgsql-hackers@lists.postgresql.org; Wed, 28 May 2025 07:51:21 +0000 Received: from mail-ed1-x532.google.com ([2a00:1450:4864:20::532]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uKBZG-000LOl-1t for pgsql-hackers@lists.postgresql.org; Wed, 28 May 2025 07:51:20 +0000 Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-6021b8b2c5fso8054822a12.2 for ; Wed, 28 May 2025 00:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1748418676; x=1749023476; darn=lists.postgresql.org; h=message-id:date:content-id:mime-version:subject:to:from:from:to:cc :subject:date:message-id:reply-to; bh=MZARKnAL6+gQHC9lHNVsOe4CUHbEwpkInO6LbVwpXB0=; b=Z/EHL/2eryogPt9NmS1+XYSqNflJEW0Gky+cRAG9hgQ1Qj6iCl1+CjcGg3XlPpPKjM aIK5IxfaE24y8fIv2skssJ4j7uPwu95MSMB8oAxoKOv0IrdkHKv0gKyk3SCYOFQdjkjI 4BX1GV41LyC4DPPqS9tNWFJSolQcIfQFZVDy/8Mo0B5WXZ82Ckax4rxBpsW1J58/CCmQ TyXsZ9YYa4BC1ZVlaHM9XUgrIVuDEH/++9O3ICTlBVj5luJD8WmS8qmcF3NzUhhHfJ54 qbc3G/2WJeurjloyCywWsZI7oaEuIAJqmj+dHw8SqHmqSvV3Ist9Rs2zkNT6+EHUs8BW lvzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748418676; x=1749023476; h=message-id:date:content-id:mime-version:subject:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MZARKnAL6+gQHC9lHNVsOe4CUHbEwpkInO6LbVwpXB0=; b=L3TnYybU0FpLtbUSnC548YqRPNnRElzWMDWtPHoaq0KGUYhFKQh18qkNkYvkIEVLGY VCLKky1fzBZpzGP65gWmMdbkQnFy+PX/4/wUY0SVG5qQMX29QSN4j8Y76VfXV31YeI55 zVZleZbfydGql6t0CVqMYGB0XVI5Qkkhrvl3rEcdwJ397CL9RikLpI1bINpzB7c1waZY aL//mraM/ohKX1JBpyFJkHrECKchAGkkVdFlKdxeL8VOM5W5JDP80lnVgDXJcqJAye8w qepJhWSDv34us0l/C8UxpVUonhVPe1DNjmzwlSPr2Rsk3InPUtMTkDiOKtjsvr69ZSPk PPYg== X-Gm-Message-State: AOJu0Yw2uhF5g5VTa0rNCES1GlbdC60aYEvooLXnsBatZWZWCKqTewN0 5QZ/HN9o9xg89q6jmhFznSppWmP/3MtzPjsA4I0Mcr1ly2IrTLDcdgALd/A0kpG/C/PLVXOtB0L 6+k3I X-Gm-Gg: ASbGncutervyQ81dt4Xdi/jKLzttEP7fHc2wWhM0E5V0aiG9bhDK7w72M59hbqXwWfh N1CJyt8JZU68Z2X/gGOsHSBucbWcv6dsBGMNF6YHvxyo0pPoDcY+DQFvU7zK04IfcNQCcQpmoW/ 15Or0C3brzoQCGkkv82g2w0TJ/Fh19CxXh3uEdSEJ3GLZaxBFTFE717hzEwhISYv7XSgMp48xrr +/n2kppu5FZum9P78h5OV0rg7HYaGY1JGkguiyvVZNUQNvUGrwHmkRSZB7Z8+zlOUn1TeDAa/Dh 7aXgbhd/fQsv7HkKAhWirLP57I+GS9ZBY0OgUDx3igNfQlcQ4fQE/OFRqUFZoSHrjQ== X-Google-Smtp-Source: AGHT+IG9TmB587QoliuA+WWejJEP1y7FJGSlPFgQPT3O4raxqYXK1xpSuM8ZTNvmt1YzAZcRJzYj4Q== X-Received: by 2002:a05:6402:2746:b0:5fc:bff8:c60a with SMTP id 4fb4d7f45d1cf-602da305236mr12636969a12.26.1748418676085; Wed, 28 May 2025 00:51:16 -0700 (PDT) Received: from localhost (109-81-168-168.rct.o2.cz. [109.81.168.168]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-6051d5f7e26sm406447a12.26.2025.05.28.00.51.15 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 May 2025 00:51:15 -0700 (PDT) From: Antonin Houska To: pgsql-hackers@lists.postgresql.org Subject: Foreign key validation failure in 18beta1 X-Mailer: MH-E 8.6+git; nmh 1.8; GNU Emacs 28.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26982.1748418675.1@localhost> Date: Wed, 28 May 2025 09:51:15 +0200 Message-ID: <26983.1748418675@localhost> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I've come across an unexpected ERROR during validation of FK constraint in PG 18beta1. The same works in PG 17: drop table if exists fk; drop table if exists pk; create table pk(i int primary key) partition by range (i); create table pk_1 partition of pk for values from (0) to (1); create table pk_2 partition of pk for values from (1) to (2); insert into pk values (0), (1); create table fk(i int); insert into fk values (1); -- Works if the FK constraint is created as valid. --alter table fk add foreign key(i) references pk; -- Fails if the FK constraint is created as NOT VALID and validated -- afterwards. alter table fk add foreign key(i) references pk not valid; alter table fk validate constraint fk_i_fkey; -- Antonin Houska Web: https://www.cybertec-postgresql.com