Re: Postgresql Query

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: "Bansal, Abhishek (Abhishek)" <bansal7(at)avaya(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql Query
Date: 2019-08-19 13:39:20
Message-ID: CAHyXU0wBJpF4FAw8K0T5i2JwExFZjH2x9tLjh+yOomhRw=QVPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Aug 19, 2019 at 2:15 AM Bansal, Abhishek (Abhishek)
<bansal7(at)avaya(dot)com> wrote:
>
> Hello, Team,
>
> Am running into a hard situation where few files are emptied with the below directory of the PostgreSQL.
>
> The files marked as red are emptied which caused server behaving very bad, could you please let us know if there is any way we can retrieve these emptied files?

The data is probably gone. It's possible some of all may still reside
in the underlying disks depending how it was deleted and how much disk
activity has occurred since the deletion event but the restoration
process would be very complex with low chance of recovery.

If the database is allowing queries, Inside of the system catalogs,
you can figure out which tables those files are attached to; it looks
like two tables were impacted. The number before the period can be
matched against pg_class.relfilenode. Once you've identified the
tables, you need to restore them from backup and get the database back
in shape assuming you can't or don't want to do a full database
restore from backup. What happens so that he files were emptied?

merlin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-08-19 14:07:25 Re: BUG #15961: psql should be able to read password from stdin
Previous Message PG Bug reporting form 2019-08-19 13:22:37 BUG #15966: Docs: