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 14:51:02
Message-ID: CAHyXU0x0Ys2z_a-P_XFVkTmK6qmO8-TGRY8zyap5k+7Yr59NBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Aug 19, 2019 at 9:18 AM Bansal, Abhishek (Abhishek)
<bansal7(at)avaya(dot)com> wrote:
>
> Hi, Merlin,
>
> Thank you for the reply
>
>
>
> When files are emptied then it caused the outage for other servers using this server as a administration. The files were emptied because the disk space was keep increasing due so we emptied these files which eventually reduced the disk size however it caused another issues
>
> Below is the directory where the files are emptied
>
> /var/lib/pgsql/data/base

OK, your data is gone. Essentially, you destroyed it; making any
direct change to the files is extremely dangerous particularly if the
database is running. The right we to free space is to delete data
from the database at the SQL level and do maintenance operations (like
VACUUM FULL or CLUSTER) to mange the files down in terms of size.

I'm sorry fo the bad news but now it's time to move ahead. Since the
database volume is full there are no likely recovery options except to
restore the impacted from backup. With some effort you may be able to
get the current database back to a consistent state so that you may be
able to restore specific tables (rather than a full restore) but this
requires in depth knowledge of database internals. If you have no
database then the only way forward is to likely to do emergency
recovery to grab out everything that is salvageable and get a
consistent database back up.

merlin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bansal, Abhishek (Abhishek) 2019-08-19 15:03:31 RE: Postgresql Query
Previous Message Thomas Kellerer 2019-08-19 14:18:24 Re: BUG #15961: psql should be able to read password from stdin