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 1nPUZt-0008Vb-VP for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Mar 2022 19:24:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nPUZs-0007q6-OQ for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Mar 2022 19:24:00 +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 1nPUZs-0007pw-Er for pgsql-hackers@lists.postgresql.org; Wed, 02 Mar 2022 19:24:00 +0000 Received: from anastigmatix.net ([68.171.219.55]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nPUZo-0005Se-EN for pgsql-hackers@lists.postgresql.org; Wed, 02 Mar 2022 19:24:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=BwQGKoOaPJhKOnmdvMm0ecX1O3lGxzEDYA0bCdjSv3s=; b=tnRaDLZwBYONxvJJja4hGu9DUD 7ZlTGva6cN9xBjgRXRfRvFu058I5+vSK8N8bmh51FVtwral5M31xTweEe3vxHoD0NXI+I/PMnPeA5 yJJxQcozwpOgANQd/qjXHNoYGzpLHYaWmwdCbMOCvuelJnSga1f+VZaWYDViWTvPNX9cYRTNSATma zk+6PLVQvPPLbFtLMvX6zpkBKneaakSSaMvaVAUkbLj9lfpiNxaSOXKCHnFEoQW57Pvd05nPnZYTm hGyoO1OXkjLGQ4arPjysloaqYycF2BhureLKwFmNn+mf8zc0lq+nk2crV6als6QeH56Z3on0HrVHP rY8X0IbQ==; Received: from 50-102-16-206.prtg.in.frontiernet.net ([50.102.16.206]:49104) by bay.acenet.us with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nPUZl-000qb9-KP; Wed, 02 Mar 2022 14:23:54 -0500 Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file To: Nathan Bossart , Stephen Frost References: <20220226220614.GA673898@nathanxps13> <20220301055100.GA1002387@nathanxps13> <621E4529.1090601@anastigmatix.net> <20220301173208.GB1031413@nathanxps13> <1f685b3a-7ec2-825e-bb2b-d87d78ad5bd9@pgmasters.net> <621E6C2E.2050801@anastigmatix.net> <20220301191441.GW10577@tamriel.snowman.net> <621E7A5C.1030203@anastigmatix.net> <20220301200523.GX10577@tamriel.snowman.net> <20220302010302.GA1182956@nathanxps13> Cc: David Steele , pgsql-hackers@lists.postgresql.org From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <621FC447.90502@anastigmatix.net> Date: Wed, 2 Mar 2022 14:23:51 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <20220302010302.GA1182956@nathanxps13> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 03/01/22 20:03, Nathan Bossart wrote: > Here is a new version of the patch with the following changes: I did not notice this earlier (sorry), but there seems to remain in backup.sgml a programlisting example that shows a psql invocation for pg_backup_start, then a tar command, then another psql invocation for pg_backup_stop. I think that was only workable for the exclusive mode, and now it is necessary to issue pg_backup_start and pg_backup_stop in the same session. (The 'touch backup_in_progress' business seems a bit bogus now too, suggesting an exclusivity remembered from bygone days.) I am not sure what a workable, simple example ought to look like. Maybe a single psql script issuing the pg_backup_start and the pg_backup_stop, with a tar command in between with \! ? Several bricks shy of production-ready, but it would give the idea. Regards, -Chap