Re: by mistake dropped physical file dropped for one table.

From: Rambabu V <ram(dot)wissen(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: by mistake dropped physical file dropped for one table.
Date: 2018-03-06 13:27:18
Message-ID: CADtiZxp5i6U0ON5H8PWRAE0NZmGr1MqnK68XiKnSNbbZOVKTnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Ok, thanks.

On Mar 6, 2018 6:51 PM, "Stephen Frost" <sfrost(at)snowman(dot)net> wrote:

> Greetings,
>
> * Rambabu V (ram(dot)wissen(at)gmail(dot)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
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message ldh@laurent-hasson.com 2018-03-10 23:42:37 RE: Updating large tables without dead tuples
Previous Message Stephen Frost 2018-03-06 13:24:25 Re: need meta data table/command to find query log