Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etCX9-0005Mr-C4 for pgsql-performance@arkaria.postgresql.org; Tue, 06 Mar 2018 13:21:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etCX8-0003Uk-9o for pgsql-performance@arkaria.postgresql.org; Tue, 06 Mar 2018 13:21:34 +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.89) (envelope-from ) id 1etCX8-0003Ua-2P for pgsql-performance@lists.postgresql.org; Tue, 06 Mar 2018 13:21:34 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etCX0-0000Ce-QU for pgsql-performance@postgresql.org; Tue, 06 Mar 2018 13:21:33 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 9EAD15F79C; Tue, 6 Mar 2018 08:21:24 -0500 (EST) Date: Tue, 6 Mar 2018 08:21:24 -0500 From: Stephen Frost To: Rambabu V Cc: pgsql-performance@postgresql.org Subject: Re: by mistake dropped physical file dropped for one table. Message-ID: <20180306132124.GL2416@tamriel.snowman.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FtAwfbRT+dym8Dt1" 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 --FtAwfbRT+dym8Dt1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Rambabu V (ram.wissen@gmail.com) wrote: > by mistake one physical file dropped for one of our table, as we do-not > have backup for this table we are getting below error. >=20 > ERROR: could not open file "base/12669/16394": No such file or directory >=20 > please help us to recover the table. You're not likely able to recover that table. To do so would require completely stopping the system immediately and attempting to perform filesystem maniuplation to "undelete" the file, or pull back chunks from the filesystem which contain pieces of the file and attempting to reconstruct it. If you've been keeping all WAL since the beginning of the cluster, it's possible you could recover that way, but you claim to not have any backups, so I'm guessing that's pretty unlikely. Thanks! Stephen --FtAwfbRT+dym8Dt1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJanpXUAAoJEO1sijiDR2RVbzcQAKd4/XdQEQ5hKXsGDmVvcB+c d1VuHLf20tmLMlQXLdCf7/sOgCZJAvZ8+1pnyOr7v1aWCNFB1vObfETQZwOB0Y8a Elo3NIc+9yoX9+jT7Y75gjeQZbD41e2Dlz0/vAvV8k1jDOfaazVpZanc3+iNV/Zo sCvcwTRwt2zpuEpOpkybzNTE0P+Wg/gn2gQbfUJMbH7rhH9CfLRX23nvhHs48EHC b1NMSxt7zp658NdbK+FhTD7wI5fHU5gWjOZmzcrV51iuXkFdTXRtqpoqWdjVgb41 3QpvcUne3m/VA6YEWNMDG/NmYhcUJaC681LAa2Fn0BwedJP5WXYwyc/6VGqvsUbl Vy0W3j/vMzL+20abQk/Q+SUP+NnxOAfRceZUr1wqNxoFLmDXW31RMojCIuum/w2W PbIKmA6Sq3Yy3hLLV8YeMmhFEaq1/3J/OBF4zMDL39d3Zr4gkqwfBhjiS0y022c/ S1dmVUI+PFe0RNb+qhw7p8I2kmX6Zw1ONaMotbws69KzSVElW54SnyU/XUioKW1e AwH2vSsjFfwQhZWkD1NDsfhKFlYY4JdNsbjSvjt7DYaTUhoSoyA+/u/kTnDVlB02 0CLziT8L4q5clKepAnLw9fQvw6n8mlLFmvtwPUgZcIXlE/b/rAO1g0kIraPJmZMq EQNPJcK0xF6GXpVGJclK =eu3I -----END PGP SIGNATURE----- --FtAwfbRT+dym8Dt1--