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 1t6TuG-00DGst-Bh for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 12:04:04 +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 1t6TuC-000eEI-Ss for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 12:04:01 +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 1t6TuC-000eE6-Hl for pgsql-general@lists.postgresql.org; Thu, 31 Oct 2024 12:04:00 +0000 Received: from wolff.to ([98.103.208.27]) by magus.postgresql.org with smtp (Exim 4.94.2) (envelope-from ) id 1t6Tu9-003znn-Sb for pgsql-general@lists.postgresql.org; Thu, 31 Oct 2024 12:03:59 +0000 Received: (qmail 3689 invoked by uid 500); 31 Oct 2024 11:38:32 -0000 Date: Thu, 31 Oct 2024 06:38:32 -0500 From: Bruno Wolff III To: pgsql-general@lists.postgresql.org Subject: COPY documentation with regard to references constraints Message-ID: <20241031113832.GA3409@wolff.to> Mail-Followup-To: Bruno Wolff III , pgsql-general@lists.postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I was unable to find any documentation clarifying if using COPY to load a table with rows referencing others rows in the same table, whether I had to worry about ordering of the input. What I found (in 17) is that even if the references constraint wasn't set as deferrable, I could have rows for children before their parents in the COPY data and things still worked.