Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e9CJE-0006tm-SU for pgsql-admin@arkaria.postgresql.org; Mon, 30 Oct 2017 15:49:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e9CJD-0005dC-Jk for pgsql-admin@arkaria.postgresql.org; Mon, 30 Oct 2017 15:49:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9CHP-0002Pl-5C for pgsql-admin@postgresql.org; Mon, 30 Oct 2017 15:47:11 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e9CHL-0001wZ-IF for pgsql-admin@postgresql.org; Mon, 30 Oct 2017 15:47:09 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 7271D5F797; Mon, 30 Oct 2017 11:47:06 -0400 (EDT) Date: Mon, 30 Oct 2017 11:47:06 -0400 From: Stephen Frost To: Marcin Koziej Cc: "pgsql-admin@postgresql.org" Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG Message-ID: <20171030154706.GE4628@tamriel.snowman.net> References: <1070071508952614@web46j.yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bb+0QjnHIYDCRDFB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --bb+0QjnHIYDCRDFB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * Marcin Koziej (marcin@cahoots.pl) wrote: > Now it's fixed, but if anyone needs I'm attaching all scripts to 1) > backup and restore wal's and 2) backup and restore base backup from > OpenStack SWIFT Interesting, but these scripts seem to be seriously lacking in error checking (what happens if the copy to swift fails..? or pg_basebackup fails?) and it's unclear how you can be sure that the WAL file has been sync'd to disk which is important or you might end up having holes in your WAL stream if the swift system fails. There's also no checking to make sure that the WAL needed for a given pg_basebackup ever actually made it to the swift system, which is required to ensure you have a consistent backup. Generally speaking, these kinds of scripts really aren't a good choice for doing backups of PG. I'd strongly suggest you look at one of the existing tools which are developed specifically for doing backups of PG and are well tested, supported, and maintained. If you'd like support for a new storage system, I know that at least pgBackRest's storage layer is pluggable and adding a new storage option is pretty straight forward. Thanks! Stephen --bb+0QjnHIYDCRDFB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJZ90l6AAoJEO1sijiDR2RVBWsP/A9Qx/TOVpaOZz7QQGSBburI D15hluHeWB/HojB5r04bRqYgjyhVRvi/u0J/x2N4aJQ6JJRRUHb/sQ7kP7V6aqR/ 3hi4LHJarOY24NvzIPizPSFyuq56E5bYbXqzoGFcqErtnLbBQTq7rLfMD+kXvTV1 TyQUCCdRtHTRLPYVKAanc9iwF2vFR64nvqtldUSzwuuLuH0Wis478fWcI3lAVxeu UqBuaSA3exvXWNWps6Vj3jilSPLmZD+3f0DmWgND3urZGjcXAnLnMoaDs25F0Koy nnzxnSrDLyhCMxffz6bxZ5s8unhcNvJR8scAWlxIeWumc/d+4I8jP7qub30zpXHv /in2yawXqDCJzNCjKBHaELq/Y7JU43ZkzmUcVhx4swbJ54KnIA6aZkycLXgUQcNp z80Nq85i6Ss/SQW2xYsNB2yVgeAIUQfvPdN26PZ9d6BAGr+yvhSAuUU2NWjPdzRj XluLqGfXJM3012Mn/brhXiP9KOxhaA2A28cjv6gwQ7Qs/C6+Pqub3LdrLeFuSBJG 8y6xE2Eso6pTJbTiWUCJGOeF3AvS8QeQATd9XBwzFU47atCyTN5VFNdVHziwD9Kb wWPM+r63nAsnAb3AZYBkxPi7z5a1zVMfebqWGZ6aWCl8JMw6Yx76kYYKF13dKtNB IJr1cmKs6JZQYVt3RKQT =FSeo -----END PGP SIGNATURE----- --bb+0QjnHIYDCRDFB--