Thread: by mistake dropped physical file dropped for one table.
Hi Team,
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.
ERROR: could not open file "base/12669/16394": No such file or directory
please help us to recover the table.
Regards,
Rambabu Vakada,
PostgreSQL DBA.
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. > > ERROR: could not open file "base/12669/16394": No such file or directory > > 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
Attachment
Ok, thanks.
On Mar 6, 2018 6:51 PM, "Stephen Frost" <sfrost@snowman.net> wrote:
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.
>
> ERROR: could not open file "base/12669/16394": No such file or directory
>
> 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