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.96) (envelope-from ) id 1vnHdo-004csu-2z for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Feb 2026 14:44:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vnHdn-005B12-38 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Feb 2026 14:44:31 +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.96) (envelope-from ) id 1vnHbN-0057ad-1n for pgsql-hackers@lists.postgresql.org; Tue, 03 Feb 2026 14:42:01 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vnHbL-00000000N1x-2LE4 for pgsql-hackers@lists.postgresql.org; Tue, 03 Feb 2026 14:42:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 613EfsVE1226621; Tue, 3 Feb 2026 09:41:54 -0500 From: Tom Lane To: Shinya Kato cc: PostgreSQL Hackers Subject: Re: Add LIMIT option to COPY FROM In-reply-to: References: Comments: In-reply-to Shinya Kato message dated "Tue, 03 Feb 2026 22:49:14 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1226619.1770129714.1@sss.pgh.pa.us> Date: Tue, 03 Feb 2026 09:41:54 -0500 Message-ID: <1226620.1770129714@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Shinya Kato writes: > I'd like to propose adding a LIMIT option to COPY FROM, which limits > the number of rows to load. Do we really need this? Each random feature we load onto COPY slows it down for everybody. regards, tom lane