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 1rSchc-00EroE-0B for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 12:50:00 +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 1rScgc-004fcT-7X for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 12:48:58 +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 1rScgb-004fcL-Vg for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 12:48:57 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rScgZ-003T6v-ON for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 12:48:57 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1482:3660:b7d0:f584:a987:bc23]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 4TKkKf2XwGz3G3B; Wed, 24 Jan 2024 13:48:54 +0100 (CET) Date: Wed, 24 Jan 2024 13:48:54 +0100 From: Christoph Berg To: Casey Shobe Cc: PostgreSQL Bugs Subject: Re: Misleading/inaccurate error message from pg_basebackup Message-ID: References: <4BA56D22-D93A-401A-BE64-97B1CC3B27A4@osss.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BA56D22-D93A-401A-BE64-97B1CC3B27A4@osss.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Casey Shobe > Below is pasted my initial message, which gives more context and detail. Let me know if anything is still inclear after this. The context is that I use Patroni to run a multi-node cluster, and WAL-G creates a hidden directory within the wal directory which I did not initially notice when I otherwise emptied it before reinitializing a node after replacing disk for the data volume. This led to a fair bit of time wasted looking for the wrong problem: I did reply to your initially message and all the questions are still open. Christoph