Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpfLh-0002Wz-SO for pgsql-general@arkaria.postgresql.org; Tue, 14 Aug 2018 19:51:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fpfLe-0007he-VF for pgsql-general@arkaria.postgresql.org; Tue, 14 Aug 2018 19:51:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpfLe-0007hS-GV; Tue, 14 Aug 2018 19:51:22 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fpfLX-000272-Fe; Tue, 14 Aug 2018 19:51:20 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1fpfLR-0007Gq-6D; Tue, 14 Aug 2018 15:51:09 -0400 Date: Tue, 14 Aug 2018 15:51:09 -0400 From: Bruce Momjian To: Rui DeSousa Cc: Benedict Holland , Bear Giles , Evan Bauer , bejita0409@yahoo.co.jp, "pgsql-admin@lists.postgresql.org" , "pgsql-general@lists.postgresql.org" Subject: Re: How to revoke privileged from PostgreSQL's superuser Message-ID: <20180814195109.GA23497@momjian.us> References: <913907.28546.qm@web103014.mail.kks.yahoo.co.jp> <26930.1533562986@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Aug 10, 2018 at 10:34:26PM -0400, Rui DeSousa wrote: > With that logic then you should use flat files for encrypted data and > unencrypted data. It’s what was done many moons ago; and its unstructured > haphazard approach gave rise to RDBMS systems. > > You cannot say that encrypted data does not belong in a RDBMS system… that is > just false. Hell, I’ve stored blobs in a RDMBS system which could have easily > been stored in a different system if need be. It’s a design choice and what > fits the application and budget needs. > > Encrypting sensitive information and storing in the database is a valid use > case. It may be only a few columns that are encrypted or a complete document > (blob); there is no need to increase complexity just to move those columns out > of the database. I think the point is that it makes sense to store data encrypted in a database only if it is a payload on another piece of non-encrypted data. You can't easily index, restrict, or join encrypted data, so it doesn't have a huge value alone in a database. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +