Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnOAM-0006Co-P3 for pgsql-admin@arkaria.postgresql.org; Tue, 16 Jul 2019 14:10:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hnOAL-00025S-Gd for pgsql-admin@arkaria.postgresql.org; Tue, 16 Jul 2019 14:10:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnOAL-000235-4H for pgsql-admin@lists.postgresql.org; Tue, 16 Jul 2019 14:10:49 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnOAJ-0003R2-12 for pgsql-admin@lists.postgresql.org; Tue, 16 Jul 2019 14:10:48 +0000 Received: by mail-oi1-x233.google.com with SMTP id l12so15670117oil.1 for ; Tue, 16 Jul 2019 07:10:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=Gf2bKHg9f0mWcd076Pa7GhnlH3oT4s8NDTXgtzRwBao=; b=iQxuaPtrUea6tAWAYlKfFHmTgeyFRaEKIPD5AitvL9tIvr3SyOp/oJZ0JIM/uxIbKk IQDprBPWA5H5FfUXiVpF9Cw9mPRZ3sVTUv5iX2ncKTuhVOYowbz8zwgROTIMVCgFliDU Du2twmhqa8T26BwvqwMJmClHSBvP0U7CpwVEnHa91udhS5607v4E+FIBCV/8K58wb5FX PLTWaNU+zK7QF76tbj52xKw4MyPM3WCiDc+45VjoiwSRkDAJ+sRiCroUEk+1kmbC86XS jPvv7r5MiR2UyxPQjPxKEoGIYk6WICNPaj0uXrj6za5K0ghEr13FFiNx1wDGq3UKYo6F gL4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=Gf2bKHg9f0mWcd076Pa7GhnlH3oT4s8NDTXgtzRwBao=; b=R9uZ27NEH3tN7Kap8oXXqYGQ4ekXLZ9+pyZXlN/C1FOJsYS0RHa6YEZd+yhqv/GVpR Uf7tkGoXp6zIuAJ+o671JN+R390zus/sOj1EwrnPoeJMCrSM0aDe5/sLHzh/tdhdjUBT jMfRnCp85uTSxocUAm96xvmi5PXvg7VIa1rWsthvAeS3Jo2TSADkvF+rSJ2UjzMrSY/c aSOeyP5U0TzYwx38kGq0Fu5MafmUOlNgxnpfM/zvknx+fHkHi5M7BiJnhjMJ+VAL6Bri rXGHJTZmn3RsHwjO5xyVfuSyDIDLnlYsanmVGbgso16/gHfGiUUG7pS2pO6uOCnJeZhI xPig== X-Gm-Message-State: APjAAAX3z03C6pIcy/AlMJMMYAkPxQ8klOSuWcaXuB5Vhy/R/Hs0rnwk hWzUUmkyE/Y9mjk1LW8X2u5FgGuY6lI= X-Google-Smtp-Source: APXvYqyLgw409UW8zlDBbMXj3rDyzwL6hnQvligr4exuHZCN5AfrSL4JgHLpibGGx7kHrlRcuCRLCg== X-Received: by 2002:aca:c7c6:: with SMTP id x189mr15195574oif.4.1563286243898; Tue, 16 Jul 2019 07:10:43 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id d17sm7221580otl.52.2019.07.16.07.10.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jul 2019 07:10:42 -0700 (PDT) Subject: Re: Unable to connect DB...? To: pgsql-admin@lists.postgresql.org References: <1fd244fa-1e3c-4f02-01ee-03a1ffd25397@jakobs.com> <1f5b6b2b-4a1f-6456-dd21-871133b5d883@jakobs.com> From: Ron Message-ID: <52b61123-aa89-bf3b-6d0f-d6e89f14d9d2@gmail.com> Date: Tue, 16 Jul 2019 09:10:39 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <1f5b6b2b-4a1f-6456-dd21-871133b5d883@jakobs.com> Content-Type: multipart/alternative; boundary="------------40BF1A7E56AA738366B137BC" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------40BF1A7E56AA738366B137BC Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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. --------------40BF1A7E56AA738366B137BC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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.
--------------40BF1A7E56AA738366B137BC--