Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWOLi-0007rW-8y for pgsql-admin@arkaria.postgresql.org; Tue, 02 Jan 2018 15:19:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWOLh-0006nN-P6 for pgsql-admin@arkaria.postgresql.org; Tue, 02 Jan 2018 15:19:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eWOLh-0006nB-Hx for pgsql-admin@lists.postgresql.org; Tue, 02 Jan 2018 15:19:29 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eWOLe-0003Aw-RN for pgsql-admin@lists.postgresql.org; Tue, 02 Jan 2018 15:19:29 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id D713F5F79C; Tue, 2 Jan 2018 10:19:25 -0500 (EST) Date: Tue, 2 Jan 2018 10:19:25 -0500 From: Stephen Frost To: Ben Primrose Cc: flumbador@virgilio.it, pgsql-admin@lists.postgresql.org Subject: Re: Issue on restore / recover Message-ID: <20180102151925.GY2416@tamriel.snowman.net> References: <524817289.230206.1514560886805@mail.virgilio.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Wn0J+vu9+NMIXK57" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Wn0J+vu9+NMIXK57 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings Ben, * Ben Primrose (bprimrose@tracelink.com) wrote: > How was the backup taken, and what platform are you on? Good questions, I've asked them also. > Are these tables in unlogged mode? Check pg_class.relpersistence to find > out. [...] > > db4=# select count(*) from pgbench_accounts ; > > > > ERROR: could not read block 1999996 in file "pg_tblspc/16471/PG_9.4_201409291/16474/16593.15": > > read only 0 of 8192 bytes PostgreSQL knows how to handle unlogged tables when doing backup/restore (they'll get zero'd out during the restore process) and so you wouldn't (shouldn't anyway) see an error like this even if the table is unlogged (instead, it would just be empty). Thanks! Stephen --Wn0J+vu9+NMIXK57 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJaS6L9AAoJEO1sijiDR2RVsrgQALK0hedPP2He9yJy5y9K4ie6 M0NgbUCVIFz31uf/WQ1vMr9jbYteUVVLRf+15k82c7fTyhEI3AuyT0vgUTP1QVH3 3+vkn+hMQMa0o155mY1CKu4PMQBPdfJvr4WqpA27uYazWX1IIYwVNNum7IyPA5nT d0rjdjYVSfh5TmJ5sV8zEx6eQfZfkCpNgeVKbkDsS9X1zDkZ8gA6PynSw9mNxcH8 IY6Yql4zRYrZ9W/jKW2jSOz/6wSFZ1GdW8eoJo4CTaz5fWifh4kX4vA4F6KW9iNc k7uYwPhqw8vVK6MwBMA0Agsc6NUan0wNHt0BatV0QitTWV3qyRbm1cAPQTXV/80B ICUT4YUM6JyCsKDkeLPCAdqQXXxYDfBiF9vP4x9ODiJPRRnfYqmL+n/J6AO7fF85 MNLrr0XhPy8CzlaC0BTYttucoiqEwyZS9uqSbj+E457vn423KQdpdONegKyWI8K9 +YE70szgYm46kpK69V5JAACd8C7T7eO2HU8DNIb3Cr8rRb0HND6kAp3oOzUSKAzq PRc3lSr0Lhej9ASNIyuz83n8rdin4+wh8wr1urTAAL7dPPQj/Ff00+L72y1nQx6x VteeYKaSVEtZuZOVI5zCCvlKzdlsH4v0NZKiWc/X5v3G8Cysvr1HeCIffCTP57wk E6nmjwM2Ml7qSGd2QpYl =pLw0 -----END PGP SIGNATURE----- --Wn0J+vu9+NMIXK57--