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 1ptgKq-0000cC-Bf for pgsql-admin@arkaria.postgresql.org; Tue, 02 May 2023 03:05:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ptgKp-0004YJ-29 for pgsql-admin@arkaria.postgresql.org; Tue, 02 May 2023 03:05:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ptgKo-0004Y9-Ng for pgsql-admin@lists.postgresql.org; Tue, 02 May 2023 03:05:46 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ptgKm-0002wc-9D for pgsql-admin@lists.postgresql.org; Tue, 02 May 2023 03:05:45 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4Q9Q1v5wRZz9sX0; Tue, 2 May 2023 05:05:39 +0200 (CEST) Date: Tue, 2 May 2023 05:05:39 +0200 (CEST) From: Erik Wienhold To: richard coleman Cc: pgsql-admin@lists.postgresql.org Message-ID: <525021224.1417508.1682996739307@office.mailbox.org> In-Reply-To: References: <6EF026A5-5CEC-48AB-B27E-C225DAE6E10A@elevated-dev.com> <491f094b-93f9-6a7d-1846-901aa583171c@gmail.com> Subject: Re: pg_dump why no indicator of completion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 02/05/2023 04:42 CEST richard coleman wrote: > > I'm glad that I was able to bring you a modicum of joy. I find this entire thread entertaining. > Backups have to be on a manual basis for the time being when I can schedule > enough time away from the users to complete it. Manged a 2.2T database this > afternoon, it only took about 10 hours with pg_dump in the database format > running 7 jobs. Differential/incremental backups with Barman or pgBackRest can cut down on this time. > Amazingly, my WAL folder has yet to fill up, I guess I must be doing it wrong. Of course there's not much WAL activity if you schedule your backup for a time window with low client activity. -- Erik