Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAbzN-0005pf-Q2 for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jan 2022 18:16:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAbzM-0007xo-Ez for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jan 2022 18:16:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAbzM-0007xf-2U for pgsql-admin@lists.postgresql.org; Thu, 20 Jan 2022 18:16:48 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nAbzK-0006mY-17 for pgsql-admin@lists.postgresql.org; Thu, 20 Jan 2022 18:16:47 +0000 Received: by mail-ot1-x32a.google.com with SMTP id n22-20020a9d2016000000b0059bd79f7777so8223415ota.2 for ; Thu, 20 Jan 2022 10:16:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ClomRcOD1QMK9cMQbeTyZJX86ovDeKufu4Oh6QtRkcM=; b=N9wz+EyBRd+4a0MN7Hq4b1Veqr9rVjDHbncdPI6qVxc2jwDjF8FVFceDOBrMfGv34k kcxbV0CUgxlhtaGf32SUqPM8v6DDA7Ktz9geQGde0vpcqot7NCDa0YV+PsIOpa3KN3tw go24xB1UFXhfA9i805scF1mabYwCBkknkdw/2bAloVHlmW1Gga94mFbOuwOXiMCIMjD1 jSZNwZuVxMepRJFvf5Fi5de3KP6H6h7lLVuAbQOVEjOtPhAd/pBemSuvn6aofMycs43B VxlWCzCr1U6y6rE+iVFVqU2zzFGdvVg4Pbk6MzaTx6q9tKxCGelM9eSlgM2J56dKfkO3 El/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ClomRcOD1QMK9cMQbeTyZJX86ovDeKufu4Oh6QtRkcM=; b=gQJkgBQwvuuYt4oQNHgBslRSF6QO0VoO9OHTPLcngSAqyiUwmfHUwQp3ksnErih84D c1WwVi2WJ8H/ZEaEscTz4DhUZWrkF4zN1AnDnR5Md0EX0juztWmGjvMixwmBSpBleS9K b/vcUm3SqDtAJkWD4J0N3VV0ddYfTe1jrXdxfI1LoDbzBzXDfFRoKhArNF/yrSeiTOXD kJ/Po6+vQK4zm3ZEowbI8HkLwZoEoNSu1bPlpte9n5rQ/nc5x4/Pr0xGwtrrp55VE6NW QkEwgXMMp3kg6QXlE8sxwz96T7v/9SMliDYel8W1ZQn9Sllx38DrEXTFieHOdk6r3Zqq IW6Q== X-Gm-Message-State: AOAM532D4EqpjtcnugEOvT5Z0T4g5h7PbWRb28WSjhf+qaCBegtZLlgs acYuDRKc+peVc+oj198Crezsey1QZVc= X-Google-Smtp-Source: ABdhPJyIqgRZOAHI6l4rCijPHI/K8FSDPAtB4Ue/t267yJZPwp7Np3Tvg8PAo+4hFm+poSbYflZr/A== X-Received: by 2002:a9d:57cd:: with SMTP id q13mr20875928oti.125.1642702603902; Thu, 20 Jan 2022 10:16:43 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id s13sm1395244ooq.3.2022.01.20.10.16.43 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Jan 2022 10:16:43 -0800 (PST) Subject: Re: Gauging progress of COPY? To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <40d1f57f-7732-108b-8475-20fec24d8748@gmail.com> Date: Thu, 20 Jan 2022 12:16:42 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/20/22 12:00 PM, Wells Oliver wrote: > Is there some clever way to gauge the progress of a COPY command? i.e. you > know it has 10m rows, but you can't SELECT COUNT(*). Use a specific tool like pg_bulkload. -- Angular momentum makes the world go 'round.