From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Unable to connect DB...?
Date: Tue, 16 Jul 2019 09:10:39 -0500
Message-ID: <52b61123-aa89-bf3b-6d0f-d6e89f14d9d2@gmail.com> (raw)
In-Reply-To: <1f5b6b2b-4a1f-6456-dd21-871133b5d883@jakobs.com>
References: <CAJi6zqrKhy9AaO-4uXG3cH53Jst1jKfUQwnOQAh_5urb8Vwabw@mail.gmail.com>
<1fd244fa-1e3c-4f02-01ee-03a1ffd25397@jakobs.com>
<1f5b6b2b-4a1f-6456-dd21-871133b5d883@jakobs.com>
Once, our developers had the bright idea of *deleting files* to quickly
purge data. Naturally, it corrupted everything, and points to the danger of
developers having the postgres password...
On 7/16/19 7:07 AM, Holger Jakobs wrote:
>
> Since your message says that the file is completely missing, someone must
> have deleted the file. There is nothing you can do except restoring from a
> backup.
>
> Making sure postgres owns the files and the access rights are restricted
> to rw------- prevents this.
>
> Even a file system error won't lead to this situation, as typically the
> file remains with length 0.
>
>
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Unable to connect DB...?
In-Reply-To: <52b61123-aa89-bf3b-6d0f-d6e89f14d9d2@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox